I was recently reading a manual an Mercurial, and the author started going on about how you could make multiple clones of a project in different directories, so that you could have different project states, and then push and pull between them. And I thought “if a supposed expert is telling me to do something that baroque and ridiculous this early in the manual, I’m sure glad I’m using Git.”
However, when you read the Git manual and get to “Rewriting History”, you could come to the conclusion that “this guy is nuts and I have to reevaluate everything I read previously based on that assumption”.
Also, cloning 2 times and moving commits between those 2 can be a lot easier than rebase/cherry-fu in one copy. I usually do that when I’m called in to fix some messed-up repo.
I would still choose Git over Hg anytime, because this happens seldom enough that the other benefits outweigh it.
I was recently reading a manual an Mercurial, and the author started going on about how you could make multiple clones of a project in different directories, so that you could have different project states, and then push and pull between them. And I thought “if a supposed expert is telling me to do something that baroque and ridiculous this early in the manual, I’m sure glad I’m using Git.”
However, when you read the Git manual and get to “Rewriting History”, you could come to the conclusion that “this guy is nuts and I have to reevaluate everything I read previously based on that assumption”. Also, cloning 2 times and moving commits between those 2 can be a lot easier than rebase/cherry-fu in one copy. I usually do that when I’m called in to fix some messed-up repo.
I would still choose Git over Hg anytime, because this happens seldom enough that the other benefits outweigh it.