Uncommitted changes and merge

Guido Ostkamp hg at ostkamp.fastmail.fm
Thu Sep 6 12:24:16 CDT 2007


> Without MQ, you would have to *commit* the local changes and then merge 
> with the parent.  Future changes to the local patches would have to 
> appear in the history as standalone changesets, and some people (me 
> included) hate having to skim through tons of history to see the changes 
> of a single bugfix or feature.
>
> With MQ, you can keep as many local patches as you want, keep refining 
> and refactoring the local patches, up to the point where they are ready 
> for 'commit'.  Then you commit them locally and merge as usual :-)

As someone who seems to be regularly using MQ stuff, can you let us know 
your opinion regarding using a 'queue repository' (with 'hg qcommit' etc.) 
vs. the 'hg qsave' and 'hg restore' commands?

What is best?

Regards

Guido


More information about the Mercurial mailing list