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

[Chris Mason]

On Tue, 20 Sep 2005 15:49:17 +0200
Robin Farine <robin.farine at terminus.org> wrote:

> On Tue September 20 2005 14:01, Chris Mason wrote:
> 
> > Whoops, qnew should definitely check for changes in the tree. 
> > I'll fix this to complain and error out, which is how qpush and
> > qpop work.
> 
> I was not sure how qnew should behave, but in the case where a 
> change involves binary files (from diff's point of view), erroring 
> out looks like the best choice.

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.

Binary files aren't compatible with mq in general.  If the change can't be represented in a patch, it won't work well at all.

-chris