@maxint@programming.dev to Programming@programming.devEnglish • 11 days agoGit without a forgewww.chiark.greenend.org.ukmessage-square53fedilinkarrow-up149arrow-down15cross-posted to: programming@programming.dev
arrow-up144arrow-down1external-linkGit without a forgewww.chiark.greenend.org.uk@maxint@programming.dev to Programming@programming.devEnglish • 11 days agomessage-square53fedilinkcross-posted to: programming@programming.dev
minus-square@Kissaki@programming.devlinkfedilinkEnglish1•edit-29 days agoThey were talking about hosting the git repository via sftp - so bare file transfer - a bare repository. And how that was enough for them. While that is also hosted, and hosted through a service, it’s only a file transfer service and hosting. That means specifically without a hosted service like a forge or gerrit. Which is why I was interested in how they handle stuff that is usually done through such forges and services / hosted software.
minus-square@solrize@lemmy.worldlinkfedilink2•9 days agoOh I see. The Linux kernel has been doing fine with mailing lists (LKML) for decades, if that helps.
They were talking about hosting the git repository via sftp - so bare file transfer - a bare repository. And how that was enough for them.
While that is also hosted, and hosted through a service, it’s only a file transfer service and hosting.
That means specifically without a hosted service like a forge or gerrit.
Which is why I was interested in how they handle stuff that is usually done through such forges and services / hosted software.
Oh I see. The Linux kernel has been doing fine with mailing lists (LKML) for decades, if that helps.