maxint@programming.dev to Programming@programming.devEnglish · 3 days agoGit without a forgewww.chiark.greenend.org.ukexternal-linkmessage-square52linkfedilinkarrow-up148arrow-down15cross-posted to: programming@programming.dev
arrow-up143arrow-down1external-linkGit without a forgewww.chiark.greenend.org.ukmaxint@programming.dev to Programming@programming.devEnglish · 3 days agomessage-square52linkfedilinkcross-posted to: programming@programming.dev
minus-squareKissaki@programming.devlinkfedilinkEnglisharrow-up1·edit-21 day 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-squaresolrize@lemmy.worldlinkfedilinkarrow-up2·1 day 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.