News for hackers. Stuff that matters.
Re:Mercurial vs Git: Why Mercurial? by guard-of-terra on Thursday February 23, 2012 @05:33PM (#3627121)
Well, if I need to turn on a few extensions and download obscure python scripts just to get the minimum viable experience, I consider the "Lego" badge mine.

"it's pretty easy to hg diff your change to a file, switch branches, and then use the GNU patch command to apply your changes on top again" It feels like mercurial developers wanted to inflict pain on me, and makes me want to hurt them in return. See, it's three steps. It's four actually, because you also want to delete the diff file.

You know how many steps did it take in SVN? Zero. When you switched branch, it just preserved all your changes and applied those back. You didn't have to do anything.

Maybe it didn't work when there was a conflict - once per 100 switches. But mercurial won't let you do that - that's 100 per 100 switches.

Re:Mercurial vs Git: Why Mercurial? by wonderercat on Friday February 24, 2012 @03:50AM (#3628496)
Once again you're demonstrating that you really don't know how to use Mercurial, but feel the need to bash its usability anyway.

   hg update <branchname>
will do exactly what you want. It's even the same command as in SVN.
Re:Mercurial vs Git: Why Mercurial? by guard-of-terra on Friday February 24, 2012 @04:19AM (#3628552)
I change a file.

do

hg update default

get:

abort: crosses branches (merge branches or use --clean to discard changes)

So?