The largest Git repo

Re:The largest Git repo by alkonaut on Wednesday May 24, 2017 @01:19PM (#14411671)

Does the virtualization work equally well for lots of history as it does for large working copies?

I have a 100k commit svn repo I have been trying to migrate but the result is just too large. Partly this is due to tons of revisions of binary files that must be in the repo.

Does the virtualization also help provide a shallow set of recent commits locally but keep all history at the server (which is hundreds of gigs that is rarely used)?

[ Parent | on HN ]

Re:The largest Git repo by vtbassmatt on Wednesday May 24, 2017 @01:29PM (#14411782)

GVFS helps in both dimensions, working copy and lots of history. For the lots of history case, the win is simply not downloading all the old content.

A GVFS clone will contain all of the commits and all of the trees but none of the blobs. This lets you operate on history as normal, so long as you don't need the file content. As soon as you touch file content, GVFS will download those blobs on demand.

[ Parent | on HN ]

Re:The largest Git repo by alkonaut on Wednesday May 24, 2017 @01:38PM (#14411847)

Thanks - that sounds perfect for lots of binary history as you never view history on the binaries, only the source files.

[ Parent | on HN ]