3 ms·
I enjoyed skipping the part of the article that explains how CVS worked, because I lived it. :) CVS at the time felt like an amazing upgrade to RCS, just like
by jedberg 8y ago
I enjoyed skipping the part of the article that explains how CVS worked, because I lived it. :)
CVS at the time felt like an amazing upgrade to RCS, just like Git feels like an amazing upgrade to CVS.
I wonder though, have we reached the end? If there anything beyond Git? When I used RCS, I would always lament "it would be nice if two of us could work on a file at the same time". When I was using CVS, I'd lament, "It would be nice if two of us could work on a group of files at the same time and merge our changes".
But using Git, my only lament is, "I wish this were easier for new developers" and "it would be great if there were a standard workflow". Problem one has been somewhat solved by GitHub/GitLab, and problem two has been solved by some pretty standard git-flow tools. Neither one really demands a new paradigm in VCS though.
- jpeloquin 8y ago> Have we reached the end? If there anything beyond Git? The ability to split and merge repositories as easily as we can split and merge branches might open up some new use patterns. The particular context I'm thinking of is scientific repositories. These tend to grow in size and scope in an unplanned manner. Pieces inevitably need to be split off for a collaboration, to be made public, or because someone is changing institutions and needs to take part of the project with them.