From: Alex Riesen <hidden> Date: 2016-06-15 22:42:09
Now, how broken is that:
The message comes from one of the hooks, which are executed even
though they never meant to, because cygwin apparently uses file
content or name to detect executability (on FAT).
I just remove the hooks from repositories atm.
From: "H. Peter Anvin" <hpa@zytor.com> Date: 2016-06-15 22:42:09
Alex Riesen wrote:
Now, how broken is that:
The message comes from one of the hooks, which are executed even
though they never meant to, because cygwin apparently uses file
content or name to detect executability (on FAT).
I just remove the hooks from repositories atm.
From: Alex Riesen <hidden> Date: 2016-06-15 22:42:09
H. Peter Anvin, Fri, Oct 14, 2005 19:57:29 +0200:
quoted
Now, how broken is that:
The message comes from one of the hooks, which are executed even
though they never meant to, because cygwin apparently uses file
content or name to detect executability (on FAT).
I just remove the hooks from repositories atm.
I think the bottom line is "don't use FAT".
I'm afraid I have to. NTFS isn't much better (newly created files
still have no correct attribute) and is slower (sometimes much
slower). Not that I have a choice, anyway: it's a typical corporate
workstation locked as down as possible.
From: Junio C Hamano <hidden> Date: 2016-06-15 22:42:09
Alex Riesen [off-list ref] writes:
quoted
quoted
The message comes from one of the hooks, which are executed even
though they never meant to, because cygwin apparently uses file
content or name to detect executability (on FAT).
Is this one of the hooks we ship as examples? If so, that
means worse brokenness than just test failing. It means that
the hook is not usable in your environment.
I presume it is this line in pre-commit sample hook:
open $fh, "-|", qw(git-diff-index -p -M --cached HEAD);
Is Perl on Cygwin incapable of handle this in general, or is it
just what is on your machine being behind?
In the meantime, I've changed two things:
- Earlier, tests run in a trash/ repository that was
initialized with user's random templates. This was *wrong*.
It now uses freshly built templates that came from the
source.
- Further, hooks are disabled in the trash/ repository used for
tests. When we later add tests for hooks (HINTS, anybody
;-)), they can add their own anyway.
From: Alex Riesen <hidden> Date: 2016-06-15 22:42:09
On 10/16/05, Junio C Hamano [off-list ref] wrote:
Alex Riesen [off-list ref] writes:
quoted
quoted
quoted
The message comes from one of the hooks, which are executed even
though they never meant to, because cygwin apparently uses file
content or name to detect executability (on FAT).
Is this one of the hooks we ship as examples? If so, that
means worse brokenness than just test failing. It means that
the hook is not usable in your environment.
I presume it is this line in pre-commit sample hook:
open $fh, "-|", qw(git-diff-index -p -M --cached HEAD);
Is Perl on Cygwin incapable of handle this in general, or is it
just what is on your machine being behind?
ActiveState's Windows port of Perl 5.8.6.
$ perl -e 'open $fh, "-|", qw(git-diff-index -p -M --cached HEAD)'
List form of pipe open not implemented at -e line 1.
I think it is not implemented because of Win32 lacking fork(2).