At Wed, 17 Apr 2019 21:31:36 +0200, Johnny Billquist <bqt%update.uu.se@localhost> wrote: Subject: Re: Alternative DVCS to git: hg? > > On 2019-04-17 16:49, Hisashi T Fujinaka wrote: > > > > After using git for my day job, I find that I depend on a lot of features > > that are missing in cvs. > > And since I'm a curious person as well, it would be interesting to > hear what you use and find so useful in git that you don't have in > cvs. I can't resist throwing in my two cents worth here too! :-) With Git it is possible to manage branches, merges, and commits in ways that are not just impossible, but completely unthinkable, with CVS. Pulls (with or without a central "pull request" support like in github) from one repo to another are the big one, especially with a shared hub of some sort, be it a private server (even one without private local "fork" support), or something like Github, with its magic fork feature. This adds up to being able to mange and pull from branches from many different forks all into one local repo, then push back to a central repo again. This means collaboration with others is far easier and safer. I also find myself lost without Magit too -- it's an extremely powerful front-end for Git implemented in Emacs. The biggest win I have with it multiple times every day is its ability to very easily stage and commit selected bits of diffs across many files, and its ability to stash un-committed local changes for other operations, including for testing commits before pushing the commit. It also does all the other normal front-end UI things like graphing commit history and showing annotations of file history and related commit logs, etc., etc. (vc-annotate for CVS is nice, but Magit is even nicer and easier) SVN is a big steaming pile, though with "git svn" it can be held at arm's length (though not quite far enough that the stench doesn't still wear on one). I did some work some time ago on FreeBSD using "git svn" to keep some sanity, but the real advantage of "git svn" is that it can ease the process of converting from SVN to Git, and one should make the conversion as quickly as possible to avoid future pain. Git is too big and far too complex too, but it's orders of magnitude (many!) better than SVN. CVS was an awesome tool when it was all there was. CVS was still a very awesome and better tool when SVN came along. However CVS doesn't hold a candle to Git (nor to Hg, but Hg is long gone off my radar). -- Greg A. Woods <gwoods%acm.org@localhost> +1 250 762-7675 RoboHack <woods%robohack.ca@localhost> Planix, Inc. <woods%planix.com@localhost> Avoncote Farms <woods%avoncote.ca@localhost>
Attachment:
pgpEIWE8MasOj.pgp
Description: OpenPGP Digital Signature