Bug: hg qnew records outstanding changes desite of not specifying-f

Mark Tolonen metolone+gmane at gmail.com
Thu Apr 1 23:27:32 CDT 2010


"Kurt Granroth" <kurt.mercurial at granroth.com> wrote in message 
news:4BB5524B.5030103 at granroth.com...
> Interesting... I would see that more as an undocumented (or incorrectly 
> documented) feature rather than a bug.  That is, that sequence makes 
> perfect sense to me and acts exactly like I would expect it to.
>
> Yet you are right that the docs say otherwise.  The examples on the wiki 
> show otherwise, as well.  I imagine this behavior must have changed 
> recently and the docs were just not updated.
>
> So..
>
> hg qinit
> hg qnew patch
> <edit something>
> hg qrefresh
>
> Can now be done as:
>
> <edit something>
> hg qnew patch
>
> No need for qinit and no need for qrefresh.  That's handy to know.

It is working like that in 1.0.1 as well.  -f actually makes more sense. 
You may have forgotten to qrefresh the current patch before qnewing the next 
one, and the previous behavior requiring -f would remind you of that fact.

I think it is a bug, not a feature.

<edit something>
hg qnew patch -f

Isn't much more to type.  Forget it with this "feature" and you'll have to 
qfold to recover if you forgot to qrefresh.

-Mark




More information about the Mercurial mailing list