Personal preference is for Mercurial. I find it easier to understand and deal with. Add in that (using extensions) it can let you use SVN and Git natively, doing pushes, pulls, commits, etc, direct to the remote repositories, and you've got a winner in my book. But, git seems to be winning the DVCS battles. I'm going to start looking at it, but I don't think I'm going to like it as much as I do Mercurial.
In any case, a DVCS is very very much the way to go. They are all better than SVN and CVS, and are usually accepted as better than Perforce and other commercial solutions. In fact, I don't think I've ever seen an argument for one of the commercial ones over Hg or Git. Learning them enough to become passable with them will take you less than an hour. Learning them very well will take a day to a week of regular use. It's time well spent. On Mon, Jan 31, 2011 at 3:35 PM, Andy Bierman <[email protected]> wrote: > On 01/31/2011 09:06 AM, Christoph Zwerschke wrote: >> >> Am 31.01.2011 16:33, schrieb Christophe de Vienne: >>> >>> This is probably a stupid question, but doesn't SourceForge support >>> mercurial ? and if so why switch to git? >> >> Git has a few advantages. It's easier to get rid of unwandted commits >> (e.g. we had a large video file in the bitbucket repository which >> probably cannot be removed without recreating the repository on >> bitbucket which would invalidate the forks), it's easier to "compose" >> commits, create small feature branches and to solve the "tangled workdir >> problem" (see http://tomayko.com/writings/the-thing-about-git), and most >> of all, it's also used by the Pylons project. We want to make >> cooperation with the Pylons team as easy as possible, so we should use >> the same tools. >> > > I was talking to the author of FREEradius, and he suggested > bailing on subversion for git. He said the histories are > smaller and branch merging was easier. It was just better. > > But I didn't have the time to learn a new CVS. > From the Git WEB Page: http://gitref.org/ > > This first thing that is important to understand about Git is that it > thinks about version control very differently than Subversion or > Perforce or whatever SCM you may be used to. It is often easier to > learn Git by trying to forget your assumptions about how version control > works and try to think about it in the Git way. > > Now you guys are convincing me to think about again. > >> -- Christoph >> > > Andy > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/turbogears-trunk?hl=en. > > -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
