mq: hg qnew doesn't record changes in the patch

Ling, Xiaofeng xiaofeng.ling at intel.com
Wed Sep 21 08:02:21 CDT 2005



Chris Mason <> wrote:
> On Tue, 20 Sep 2005 18:17:56 +0200
> Robin Farine <robin.farine at terminus.org> wrote:
> 
>> On Tue September 20 2005 16:40, Chris Mason wrote:
>> 
>>> http://www.serpentine.com/~cmason now has an updated mq command.
>>> With local changes, hg qnew will error out, and hg qnew -f will
>>> proceed.  With hg qnew -f, you can run hg qrefresh to get the local
>>> changes included in your patch.
>> 
>> Since a Mercurial changeset created by 'qnew -f' can be easily
>> removed by qpop, shouldn't the refresh step automatically be
>> performed when qnew is invoked with -f?
> 
> In general, -f means 'I really know what I'm doing, don't do extra
> checks'.  For qpush and qpop, it skips the check for local changes
> (making the push or pop much faster on large repos), so I'm trying to
> be consistent in how the flag gets used.   
General speaking, I think hg qnew shall do the qrefresh by default.
As qnew will check in the changes, I originally think it will do qrefresh also.
but later I found it does not, so when I pop out the patch, the change
lost. So doing qrefresh by default it better, user will not lose any work.
otherwise, maybe many users will complain the problem.







More information about the Mercurial mailing list