Augie Fackler writes: > There is no sacrifice [for git users moving to Mercurial] other > than familiarity--and because Mercurial indeed has as simpler UI, > closing the familiarity gap from Git to Mercurial is much easier > than the other way around.
AFAIK it is still much easier to do the kinds of things that "git filter-branch" does in git than in hg. (Haven't looked closely at hg's capabilities since 3.2, though -- hg has been just fine for everyday work on hg-using projects for years IMO.) OTOH, I don't think that's relevant to Python development, and probably the majority of VCS users consider it an abomination. > If Python crew wants to go to Git, then it should go to Git, but it > should want to go for legitimate reasons--not a misguided belief > that Git can do things Mercurial cannot. +1 I've always liked git (I was the git proponent for PEP 374), but even at that time, the kinds of things that the vast majority of Python developers do the vast majority of the time were equally possible in git and hg. The only thing that hg really lost badly on IMO was "named branches", and that's been fixed with bookmarks. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
