hg qnew doesn't record changes in the patch

Ling, Xiaofeng xiaofeng.ling at intel.com
Mon Sep 19 20:06:46 CDT 2005

Robin Farine <> wrote:
> Hi,
> I am starting to experiment with the mq extension. First, what an
> awesome addition to the already wonderful world of Mercurial! It does
> exactly what I missed from many scm tools: volatile micro-branches to
> prepare series of clean changesets. And combined with Mercurial, it's
> just perfect. So, many thanks to the authors and contributors of
> these excellent tools.     
> Now back to the subject. It looks like 'hg qnew' records the patch
> creation in Mercurial by a forced commit of the current state of the
> tree. When there are uncommitted changes in the tree, they get
> recorded in the new changeset but not in the new mq patch. Later,
> when one 'hg qpop' this patch, the associated changes disappear with
> the discarded changeset. Also, an 'hg qpush' of this patch complains
> that there is only garbage in the patch file.      
> When there are uncommitted changes in the tree, it would be nice if
> 'hg qnew' either complains and errors out without taking any action
> or includes the changes in the new patch. I tend to prefer the former
> but I guess others might find the latter more user friendly.   
I have a patch that do refresh after qnew.
or you need to manually run hg qrefresh after qnew.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: qnew-refresh.patch
Type: application/octet-stream
Size: 324 bytes
Desc: qnew-refresh.patch
Url : http://www.selenic.com/pipermail/mercurial/attachments/20050920/d19b8e38/qnew-refresh.obj

More information about the Mercurial mailing list