How to use Mercurial?
TK Soh
teekaysoh at gmail.com
Sat Apr 10 20:53:34 CDT 2010
On Sat, Apr 10, 2010 at 12:01 PM, Jon Ribbens
<jon-mercurial at unequivocal.co.uk> wrote:
> On Sat, Apr 10, 2010 at 05:08:32AM +0000, TK Soh wrote:
>> IMO, it is actually a design flow for CVS and the like to do so.
>> Though, to be fair, given the design of CVS (being of older
>> technology), I am not sure there's a better way to handle this. That's
>> why I stop using it totally after starting to use Mercurial.
>
> Well, I guess my question was kind've *how* do you "stop using it
> totally" - what are you supposed to do instead?
I am not 100% clear what you are asking here. In any case, it's my
opinion that you should always commit your changes before pulling and
merging, in order to 'protect' the changes, and allow you to revert in
case there's any problem during merging (with hg merge) or that you
have a second thought.
However, if you do thing the CVS way, i.e. always have to update to
the latest rev before you can checkin, then 'hg update' is already
doing this (though IMO, the --check option should be a default ;-).
FWIW, 'back then' when I was using CVS, I always save 'cvs diff' to a
file before doing update, in case something goes wrong and I need to
back track. I no longer have to this with hg.
BTW, you should take a look at MQ if you haven't.
More information about the Mercurial
mailing list