6 ms·
Well, let's just be honest here, a 3-4 gb git repo is ridiculously huge. I'd expect everything to be slow. For reference, a full checkout of the linux kernel i
by xxpor 6y ago
Well, let's just be honest here, a 3-4 gb git repo is ridiculously huge. I'd expect everything to be slow.
For reference, a full checkout of the linux kernel is 2.5GB.
- jackewiehose 6y ago> a 3-4 gb git repo is ridiculously huge. It's an old long SVN repository with a lot of files. I would like to split it in two SVN repos but that would destroy their history. Any ideas? > I'd expect everything to be slow. It's actually very OK with git in cygwin-bash.
- universa1 6y agoYou can do the split in subversion by filtering the paths, and keeping the history :-) There is a svnadmin command for that. I guess you can do something similar in git
- namibj 6y agoThe magic is inside git-subtree (invoke as `git subtree split -P path/prefix/of/subtree/to/decouple -b branch-name-to-create-and-store-subtree-history`). There is also more exotic stuff that would just rip a complete folder out, but that get's complicated.
- adrianN 6y agoI regularly work on 10GB+ repositories and every operation is pretty much instant.
- xxpor 6y agoAre you checking in binaries or something?