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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

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

A. S. Budden
# HG changeset patch
# User A. S. Budden <[hidden email]>
# 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.

This patch adds an 'ignoreexec' option to the 'ui' field in hgrc
to allow a user to make the posix version act like the Windows
version and ignore execution mode changes.  This is roughly
equivalent to Git's core.filemode option.

diff --git a/hgext/convert/subversion.py b/hgext/convert/subversion.py
--- a/hgext/convert/subversion.py
+++ b/hgext/convert/subversion.py
@@ -1017,7 +1017,9 @@
         self.opener = scmutil.opener(self.wc)
         self.wopener = scmutil.opener(self.wc)
         self.childmap = mapfile(ui, self.join('hg-childmap'))
-        self.is_exec = util.checkexec(self.wc) and util.isexec or None
+        self.is_exec = util.checkexec(self.wc) \
+                and not ui.config('ui', 'ignoreexec', False) \
+                and util.isexec or None
 
         if created:
             hook = os.path.join(created, 'hooks', 'pre-revprop-change')
diff --git a/mercurial/dirstate.py b/mercurial/dirstate.py
--- a/mercurial/dirstate.py
+++ b/mercurial/dirstate.py
@@ -143,7 +143,10 @@
 
     @propertycache
     def _checkexec(self):
-        return util.checkexec(self._root)
+        if self._ui.config('ui', 'ignoreexec', False):
+            return False
+        else:
+            return util.checkexec(self._root)
 
     @propertycache
     def _checkcase(self):
diff --git a/mercurial/help/config.txt b/mercurial/help/config.txt
--- a/mercurial/help/config.txt
+++ b/mercurial/help/config.txt
@@ -1097,6 +1097,10 @@
     ``ignore.other = ~/.hgignore2``. For details of the ignore file
     format, see the ``hgignore(5)`` man page.
 
+``ignoreexec``
+    Ignore changes to the execution mode on files being committed.  True
+ or False.  Default is False.
+
 ``interactive``
     Allow to prompt the user. True or False. Default is True.
 
diff --git a/tests/test-execute-bit.t b/tests/test-execute-bit.t
--- a/tests/test-execute-bit.t
+++ b/tests/test-execute-bit.t
@@ -26,3 +26,18 @@
   $ test -x a && echo executable -- bad || echo not executable -- good
   not executable -- good
 
+test ignoreexec option
+
+  $ hg up tip
+  0 files updated, 0 files merged, 0 files removed, 0 files unresolved
+  $ echo b > b
+  $ hg ci -Am'not executable'
+  adding b
+
+  $ chmod +x b
+  $ hg st
+  M b
+  $ echo '[ui]' >> .hg/hgrc
+  $ echo 'ignoreexec = True' >> .hg/hgrc
+  $ hg st
+
_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel
Reply | Threaded
Open this post in threaded view
|

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

Angel Ezquerra Moreu
On Fri, Mar 2, 2012 at 1:20 PM, A. S. Budden <[hidden email]> wrote:

> # HG changeset patch
> # User A. S. Budden <[hidden email]>
> # 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.
>
> This patch adds an 'ignoreexec' option to the 'ui' field in hgrc
> to allow a user to make the posix version act like the Windows
> version and ignore execution mode changes.  This is roughly
> equivalent to Git's core.filemode option.

I find the setting name "ui.ignoreexec" a bit unclear, particularly
the fact that it stems directly from the ui section. Also it is not
clear what sort of "exec" you are ignoring.

Instead, maybe it could be called "ui.commit.ignoreexecbit"?

Angel
_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel
Reply | Threaded
Open this post in threaded view
|

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

A. S. Budden
On 2 March 2012 12:25, Angel Ezquerra Moreu <[hidden email]> wrote:

> On Fri, Mar 2, 2012 at 1:20 PM, A. S. Budden <[hidden email]> wrote:
>> # HG changeset patch
>> # User A. S. Budden <[hidden email]>
>> # 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.
>>
>> This patch adds an 'ignoreexec' option to the 'ui' field in hgrc
>> to allow a user to make the posix version act like the Windows
>> version and ignore execution mode changes.  This is roughly
>> equivalent to Git's core.filemode option.
>
> I find the setting name "ui.ignoreexec" a bit unclear, particularly
> the fact that it stems directly from the ui section. Also it is not
> clear what sort of "exec" you are ignoring.

Fair enough.

> Instead, maybe it could be called "ui.commit.ignoreexecbit"?

That's certainly easy to change... I'm not sure about the 'ui.commit'
bit though: it affects 'hg st' as well as 'hg commit': would it be
better as 'ui.ignoreexecbit'?

Al
_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel
Reply | Threaded
Open this post in threaded view
|

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

Angel Ezquerra Moreu
On Fri, Mar 2, 2012 at 1:38 PM, A. S. Budden <[hidden email]> wrote:

> On 2 March 2012 12:25, Angel Ezquerra Moreu <[hidden email]> wrote:
>> On Fri, Mar 2, 2012 at 1:20 PM, A. S. Budden <[hidden email]> wrote:
>>> # HG changeset patch
>>> # User A. S. Budden <[hidden email]>
>>> # 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.
>>>
>>> This patch adds an 'ignoreexec' option to the 'ui' field in hgrc
>>> to allow a user to make the posix version act like the Windows
>>> version and ignore execution mode changes.  This is roughly
>>> equivalent to Git's core.filemode option.
>>
>> I find the setting name "ui.ignoreexec" a bit unclear, particularly
>> the fact that it stems directly from the ui section. Also it is not
>> clear what sort of "exec" you are ignoring.
>
> Fair enough.
>
>> Instead, maybe it could be called "ui.commit.ignoreexecbit"?
>
> That's certainly easy to change... I'm not sure about the 'ui.commit'
> bit though: it affects 'hg st' as well as 'hg commit': would it be
> better as 'ui.ignoreexecbit'?
>
> Al

OK, I did not realize that.

"ui.ignoreexecbit" would definitely be better, but I still find the
name slightly generic. Does this really belong in the "ui" section.

Angel
_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel
Reply | Threaded
Open this post in threaded view
|

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

A. S. Budden
On 2 March 2012 12:42, Angel Ezquerra Moreu <[hidden email]> wrote:

> On Fri, Mar 2, 2012 at 1:38 PM, A. S. Budden <[hidden email]> wrote:
>> On 2 March 2012 12:25, Angel Ezquerra Moreu <[hidden email]> wrote:
>>> On Fri, Mar 2, 2012 at 1:20 PM, A. S. Budden <[hidden email]> wrote:
>>>> # HG changeset patch
>>>> # User A. S. Budden <[hidden email]>
>>>> # 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.
>>>>
>>>> This patch adds an 'ignoreexec' option to the 'ui' field in hgrc
>>>> to allow a user to make the posix version act like the Windows
>>>> version and ignore execution mode changes.  This is roughly
>>>> equivalent to Git's core.filemode option.
>>>
>>> I find the setting name "ui.ignoreexec" a bit unclear, particularly
>>> the fact that it stems directly from the ui section. Also it is not
>>> clear what sort of "exec" you are ignoring.
>>
>> Fair enough.
>>
>>> Instead, maybe it could be called "ui.commit.ignoreexecbit"?
>>
>> That's certainly easy to change... I'm not sure about the 'ui.commit'
>> bit though: it affects 'hg st' as well as 'hg commit': would it be
>> better as 'ui.ignoreexecbit'?
>>
>> Al
>
> OK, I did not realize that.
>
> "ui.ignoreexecbit" would definitely be better, but I still find the
> name slightly generic. Does this really belong in the "ui" section.

I don't know: can you suggest a better section?  I really don't mind
where it goes.

Al
_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel
Reply | Threaded
Open this post in threaded view
|

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

Angel Ezquerra Moreu


On Mar 2, 2012 2:44 PM, "A. S. Budden" <[hidden email]> wrote:
>
> On 2 March 2012 12:42, Angel Ezquerra Moreu <[hidden email]> wrote:
> > On Fri, Mar 2, 2012 at 1:38 PM, A. S. Budden <[hidden email]> wrote:
> >> On 2 March 2012 12:25, Angel Ezquerra Moreu <[hidden email]> wrote:
> >>> On Fri, Mar 2, 2012 at 1:20 PM, A. S. Budden <[hidden email]> wrote:
> >>>> # HG changeset patch
> >>>> # User A. S. Budden <[hidden email]>
> >>>> # 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.
> >>>>
> >>>> This patch adds an 'ignoreexec' option to the 'ui' field in hgrc
> >>>> to allow a user to make the posix version act like the Windows
> >>>> version and ignore execution mode changes.  This is roughly
> >>>> equivalent to Git's core.filemode option.
> >>>
> >>> I find the setting name "ui.ignoreexec" a bit unclear, particularly
> >>> the fact that it stems directly from the ui section. Also it is not
> >>> clear what sort of "exec" you are ignoring.
> >>
> >> Fair enough.
> >>
> >>> Instead, maybe it could be called "ui.commit.ignoreexecbit"?
> >>
> >> That's certainly easy to change... I'm not sure about the 'ui.commit'
> >> bit though: it affects 'hg st' as well as 'hg commit': would it be
> >> better as 'ui.ignoreexecbit'?
> >>
> >> Al
> >
> > OK, I did not realize that.
> >
> > "ui.ignoreexecbit" would definitely be better, but I still find the
> > name slightly generic. Does this really belong in the "ui" section.
>
> I don't know: can you suggest a better section?  I really don't mind
> where it goes.
>
> Al

I don't really know. Looking at the existing sections on the hgrc wiki page I don't really see an obvious section...

To me it feels as a sort of "encode" option, but I don't think it's possible to put non patterns in that section. It is also related to the diff section, but it doesn't really belong there either...

Maybe someone else has a better idea? Otherwise I guess ui would be ok.

Angel


_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel
Reply | Threaded
Open this post in threaded view
|

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

Matt Mackall
In reply to this post by A. S. Budden
On Fri, 2012-03-02 at 12:20 +0000, A. S. Budden wrote:

> # HG changeset patch
> # User A. S. Budden <[hidden email]>
> # 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.

--
Mathematics is the supreme nostalgia of our time.


_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel
Reply | Threaded
Open this post in threaded view
|

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

A. S. Budden
On 2 March 2012 19:14, Matt Mackall <[hidden email]> wrote:

> On Fri, 2012-03-02 at 12:20 +0000, A. S. Budden wrote:
>> # HG changeset patch
>> # User A. S. Budden <[hidden email]>
>> # 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
_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel
Reply | Threaded
Open this post in threaded view
|

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

Matt Mackall
On Tue, 2012-03-06 at 09:04 +0000, A. S. Budden wrote:

> On 2 March 2012 19:14, Matt Mackall <[hidden email]> wrote:
> > On Fri, 2012-03-02 at 12:20 +0000, A. S. Budden wrote:
> >> # HG changeset patch
> >> # User A. S. Budden <[hidden email]>
> >> # 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

I am not at all interested in your diagnosis or prescription until AFTER
I hear about the details of your symptoms.

--
Mathematics is the supreme nostalgia of our time.


_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel
Reply | Threaded
Open this post in threaded view
|

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

marco gaddoni


On Tue, Mar 6, 2012 at 19:40, Matt Mackall <[hidden email]> wrote:
On Tue, 2012-03-06 at 09:04 +0000, A. S. Budden wrote:
> On 2 March 2012 19:14, Matt Mackall <[hidden email]> wrote:
> > On Fri, 2012-03-02 at 12:20 +0000, A. S. Budden wrote:
> >> # HG changeset patch
> >> # User A. S. Budden <[hidden email]>
> >> # Date <a href="tel:1330690534%200" value="+13306905340">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

I am not at all interested in your diagnosis or prescription until AFTER
I hear about the details of your symptoms.


i have this problem too.
the details are:
the repo is on win7 ntfs filesystem.
i have a repo committed with the windows version of tortoisehg
   the files in the repository are marked as not executable

in cygwin, using the python & mercurial of cygwin
(trying to avoid the bug that the windows version of python do not
detect correctly that the terminal is interactive)
I see all the files as executable.

$ hg diff Project.sln
diff --git a/Project.sln b/Project.sln
old mode 100644
new mode 100755

maybe the solution is to use the noexec option
of mount in cygwin.

 
--
Mathematics is the supreme nostalgia of our time.


_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel



--
"Reality continues to ruin my life." - Calvin.

_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel
Reply | Threaded
Open this post in threaded view
|

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

Matt Mackall
On Wed, 2012-03-07 at 11:52 +0100, marco gaddoni wrote:

> On Tue, Mar 6, 2012 at 19:40, Matt Mackall <[hidden email]> wrote:
>
> > On Tue, 2012-03-06 at 09:04 +0000, A. S. Budden wrote:
> > > On 2 March 2012 19:14, Matt Mackall <[hidden email]> wrote:
> > > > On Fri, 2012-03-02 at 12:20 +0000, A. S. Budden wrote:
> > > >> # HG changeset patch
> > > >> # User A. S. Budden <[hidden email]>
> > > >> # 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
> >
> > I am not at all interested in your diagnosis or prescription until AFTER
> > I hear about the details of your symptoms.
> >
> >
> i have this problem too.
> the details are:
> the repo is on win7 ntfs filesystem.
> i have a repo committed with the windows version of tortoisehg
>    the files in the repository are marked as not executable
>
> in cygwin, using the python & mercurial of cygwin
> (trying to avoid the bug that the windows version of python do not
> detect correctly that the terminal is interactive)
> I see all the files as executable.
>
> $ hg diff Project.sln
> diff --git a/Project.sln b/Project.sln
> old mode 100644
> new mode 100755
>
> maybe the solution is to use the noexec option
> of mount in cygwin.

I think we'll probably end up disabling exec support in cygwin by
default (and symlinks too).

See also: http://mercurial.selenic.com/bts/issue3301

--
Mathematics is the supreme nostalgia of our time.


_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel
Reply | Threaded
Open this post in threaded view
|

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

marco gaddoni


On Wed, Mar 7, 2012 at 20:10, Matt Mackall <[hidden email]> wrote:
On Wed, 2012-03-07 at 11:52 +0100, marco gaddoni wrote:
> On Tue, Mar 6, 2012 at 19:40, Matt Mackall <[hidden email]> wrote:
>
> > On Tue, 2012-03-06 at 09:04 +0000, A. S. Budden wrote:
> > > On 2 March 2012 19:14, Matt Mackall <[hidden email]> wrote:
> > > > On Fri, 2012-03-02 at 12:20 +0000, A. S. Budden wrote:
> > > >> # HG changeset patch
> > > >> # User A. S. Budden <[hidden email]>
> > > >> # Date <a href="tel:1330690534%200" value="+13306905340">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
> >
> > I am not at all interested in your diagnosis or prescription until AFTER
> > I hear about the details of your symptoms.
> >
> >
> i have this problem too.
> the details are:
> the repo is on win7 ntfs filesystem.
> i have a repo committed with the windows version of tortoisehg
>    the files in the repository are marked as not executable
>
> in cygwin, using the python & mercurial of cygwin
> (trying to avoid the bug that the windows version of python do not
> detect correctly that the terminal is interactive)
> I see all the files as executable.
>
> $ hg diff Project.sln
> diff --git a/Project.sln b/Project.sln
> old mode 100644
> new mode 100755
>
> maybe the solution is to use the noexec option
> of mount in cygwin.

I think we'll probably end up disabling exec support in cygwin by
default (and symlinks too).

See also: http://mercurial.selenic.com/bts/issue3301


works for me;
please let me hope that if I have a linux project
with meaningful exec bits i will not
risk damaging it by checking out
and commiting unrelated files in
cygwin.

 
--
Mathematics is the supreme nostalgia of our time.





--
"Reality continues to ruin my life." - Calvin.

_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel
Reply | Threaded
Open this post in threaded view
|

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

Gilles Moris
On Wednesday 07 March 2012 09:22:25 pm marco gaddoni wrote:
> works for me;
> please let me hope that if I have a linux project
> with meaningful exec bits i will not
> risk damaging it by checking out
>  and commiting unrelated files in
> cygwin.

May be this could help in some way:
http://selenic.com/pipermail/mercurial/2011-January/036537.html

Regards.
Gilles.
_______________________________________________
Mercurial-devel mailing list
[hidden email]
http://selenic.com/mailman/listinfo/mercurial-devel