[PATCH] posix: add configuration option to ignore execution mode changes (issue3301)

A. S. Budden abudden at gmail.com
Tue Mar 6 03:04:58 CST 2012


On 2 March 2012 19:14, Matt Mackall <mpm at selenic.com> wrote:
> On Fri, 2012-03-02 at 12:20 +0000, A. S. Budden wrote:
>> # HG changeset patch
>> # User A. S. Budden <abudden at gmail.com>
>> # Date 1330690534 0
>> # Node ID 105fae68f78292cebd41e118bc68b24c171fa553
>> # Parent  85db991780b7b86913c3e29a5fe7ef25ab5ee93c
>> posix: add configuration option to ignore execution mode changes (issue3301)
>>
>> Using a posix version of Mercurial on a filesystem (such as FAT)
>> without support for the executable bit can result in Mercurial
>> erroneously reporting/committing executable bit changes.
>
> I'd rather not go this route. If you know of a scenario where we record
> imaginary exec bit changes, report the details so we can work out
> whether we can avoid it.

Unfortunately, the problem is with Windows applications not knowing
anything about Cygwin permissions and hence setting the executable bit
(as far as Cygwin is concerned).  In Git I can easily work round this
with "core.filemode = false".  The only time I really have an issue
with it is with version control systems, so if I use Git there is no
problem.

If you don't want this option to be offered in Mercurial, is there any
way I could do it with an extension?  It looked a bit too 'core' to me
to be possible in an extension, but then I've never written a
Mercurial extension before...

Al


More information about the Mercurial-devel mailing list