bug: qpush loses loses file executable permissions

Chris Mason chris.mason at oracle.com
Fri Nov 3 07:54:59 CST 2006


On Fri, Nov 03, 2006 at 03:52:53AM +0200, Giorgos Keramidas wrote:
> On 2006-11-02 17:15, Armando Singer <armando.singer at gmail.com> wrote:
> > Good to know!
> >
> > I would vote for one or both of the following:
> >
> > 1. Use/enable git diffs by default when the mq extension is added (or
> >   when any mq command that works with diffs is run). That is, most
> >   things should "just work." Using qpush/qpop, etc. is not useable
> >   for common operations without this.
> >
> > and/or
> >
> > 2. Show a warning or fail whenever any command is run that could
> >   result in loss of information. Example:
> >
> >   hg qpop
> >   abort: working tree contains mode changes that will be lost
> >   (enable git diff format to retain)
> >
> >   This would include commands outside of mq.
> 
> A third option would be to extend GNU patch(1), making it able to
> automatically grok and properly handle git-format patches, and submit
> this to the GNU patch developers.  This would make it then possible to
> export --git patches from Mercurial, and patch source trees which are
> under the control of other SCM's too.

Rather than patch patch(1), I've created a standalone utility that
(thanks to Brendan) can also understand the git formats:

http://oss.oracle.com/~mason/mpatch

-chris



More information about the Mercurial mailing list