2 ms·
The man page(1) provides a good overview. Imagine a git backend with a cvs/svn front-end (which ought to make Linus Torvalds kill himself(2) just so he can rol
by ksherlock 7y ago
The man page(1) provides a good overview. Imagine a git backend with a cvs/svn front-end (which ought to make Linus Torvalds kill himself(2) just so he can roll over in his grave).
got checkout, for example, can limit itself to a subdirectory of the repository.
1. https://gameoftrees.org/got.1.html https://gameoftrees.org/got.1.html
2. "I credit CVS in a very very negative way. Because I, in many ways, when I designed git, it's "what would Jesus do" except that it's "what would CVS never ever do"-kind of approach to source control management. I've never actually used CVS for the kernel. For the first 10 years of kernel maintenance, we literally used tarballs and patches, which is a much superior source control management system than CVS is, but I did end up using CVS for 7 years at a commercial company, and I hate it with a passion.
"When I say I hate CVS with a passion, I have to also say that if there any SVN users (Subversion users) in the audience, you might want to leave. Because my hatred of CVS has meant that I see Subversion as being the most pointless project ever started, because the whole slogan for the Subversion for a while was 'CVS done right' or something like that. And if you start with that kind of slogan, there is nowhere you can go. It's like, there is no way to do CVS right."