4 ms·

GitHub makes a downloadable tarball of each repository available for download, which is nice for those who don't have (or don't want to install) Git. I underst

GitHub makes a downloadable tarball of each repository available for download, which is nice for those who don't have (or don't want to install) Git. I understand that the Postgres team isn't using GitHub, but it makes me think -- could they use an oldschool tarball to update their BuildFarm nodes who cannot run Git? Or better yet, rsync, so only changes are transferred? Anyway, this is a decent writeup. I've wondered before about large project migration to Git.

pyre 16y ago
Someone suggested that in the comments, and the reply was that the amount of bandwidth to pull down the tarball is greater than just syncing the changes. It seems like they could use some sort of centralized checkout system + rsync to pull down changes. Possibly using gitolite's master/slave mirroring functionality.
plaes 16y ago
IIRC, they even provide two-way (commit and fetch) subversion->git gateway...
- mrduncan 16y ago
  You're correct: http://github.com/blog/626-announcing-svn-support http://github.com/blog/626-announcing-svn-support http://github.com/blog/644-subversion-write-support http://github.com/blog/644-subversion-write-support