bug: qpush loses loses file executable permissions

[Armando Singer]

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.

Thanks,
Armando

On 11/2/06, Brendan Cully <brendan at kublai.com> wrote:
> On Thursday, 02 November 2006 at 14:04, Armando Singer wrote:
> > Thank you. This is what I could find in the wiki (tonfa) about turning
> > on git diffs:
> >
> >  "support for git-style extended patches, including copy/rename
> >  information, mode changes, and binary files. Most commands that
> >  generate patches now take the --git option, or it can be enabled
> >  globally in .hgrc by adding git = True to the [diff] section."
> >
> > 1. Why isn't git diff format the default? I'm not sure there was any
> >   way of knowing this config is required without breaking things a
> >   few times.
> >
> > 2. Do I lose any functionality by globally enabling this? (Before I
> >   tell all developers to make this change.)
>
> I think the main reason is that the git format isn't fully compatible
> with plain patch (though it is for diffs that don't contain copies or
> empty or binary files, I believe). This is a problem for, among other
> things, older versions of mercurial.
>
> You shouldn't lose anything by enabling it, but you'd probably have to
> run tip everywhere to get the benefit. Hopefully 0.9.2 will be out
> soon.
>