-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 19/09/14 10:48 AM, Rich Freeman wrote: > On Fri, Sep 19, 2014 at 10:25 AM, hasufell <[email protected]> > wrote: >> >> That is pretty easy and takes you ~20s for a keyword merge. >> What's the problem? >> > > Agree. Also, there was a comment that git pull is much slower than > cvs. While it is true that git does refresh the whole tree all the > time, it is FAR more efficient at doing this than CVS, since the > local and remote repositories can use a single hash to determine > where each stands relative to the other, and the COW mechanism > applies to directory trees so when making comparisons git does not > need to traverse the full depth of the tree for every branch. A > cvs update on the entire tree is basically an independent > synchronization of every file in the tree. Also, by refreshing the > entire tree you also catch any repoman errors that might result > from commits to other packages that you didn't have visibility to > when refreshing only a single package in cvs. >
That wasn't really part of his argument, though -- when he's fixing keyword collisions, he's only working within one package, and CVS in that case -only- checks the subtree as of that package (ie, ./ and ./files/) when updating. Git on the other hand will update the entire tree and there's no way around that, right? (unless of course i missed something in hasufell's command list) I don't think there's any valid debate on whether git is more efficient than cvs on fetching tree-wide updates :) > I wonder if it would make sense to set up a practice git tree > somewhere so that people can try working together on workflows/etc. > We can clone a migrated tree (I have one from a few days ago on > github). Definitely. I'd volunteer for that (doing my updates to both git and cvs trees), and I expect others would as well. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlQcR1UACgkQ2ugaI38ACPA1ogEAmn9ZBr9nORFH02cxu4HML+9C OKyPystsxAaOdEnkzS8A/29mitUtED8jowJ+5Udh9YyYRjJApzx36hRMyyAsJUVc =B0E9 -----END PGP SIGNATURE-----
