From: Junio C Hamano <gitster@pobox.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Johannes Sixt <j.sixt@viscovery.net>, Jeff King <peff@peff.net>,
layer <layer@known.net>,
git@vger.kernel.org
Subject: Re: [PATCH] disable post-checkout test on Cygwin
Date: Tue, 17 Mar 2009 13:42:31 -0700 [thread overview]
Message-ID: <7v63i7ridk.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090317202818.GA13458@blimp.localdomain> (Alex Riesen's message of "Tue, 17 Mar 2009 21:28:18 +0100")
Alex Riesen <raa.lkml@gmail.com> writes:
> Johannes Sixt, Tue, Mar 17, 2009 17:59:09 +0100:
>> Junio C Hamano schrieb:
>> > Alex Riesen <raa.lkml@gmail.com> writes:
>> >
>> >> It is broken because of the tricks we have to play with
>> >> lstat to get the bearable perfomance out of the call.
>> >> Sadly, it disables access to Cygwin's executable attribute,
>> >> which Windows filesystems do not have at all.
>> >
>> > Hmm, perhaps when checking hooks to see if they are executable, Cygwin
>> > port should avoid using the "tricks"? Compared to paths inside the
>> > worktree the number of hooks is a lot smaller, no?
>>
>> Hmm. Nowadays, we run hooks through run_hook() in run_command.c. It uses
>
> The problem is that copy_templates_1 does an lstat on the files in
> templates directory and gets 0666 mode (regular file, non-exec) for
> executable file under current Cygwin port. The st_mode of that lstat
> is passed to copy_file mentioned, which is useless now as we use the
> Win32 version of lstat, which doesn't do x-bit.
Ahhh.
I do not mind the patch as a band-aid to make the testsuite pass, so I'll
apply your patch as-is. Thanks.
But isn't this something shops that do deploy Cygwin version of git want
to see fixed, so that they can have a site-wide policy implemented in the
hooks copied from templates? I think we could pass mode 0 to copy_files()
and have the function special case it (and allow a platform specific
copy_files() implementated by Cygwin). lstat() in the copy_templates_1()
codepath is primarily done to see if we need to descend into a directory
or symlink() and our use of st.st_mode to pass to copy_files() is a no
cost side effect on platforms with x-bit support.
>> access(..., X_OK), not lstat(). We don't play games with access(), do we?
>
> access(..., X_OK) will return -1.
That codepath would also need to be fixed if Cygwin wants to use hooks, I
would guess.
next prev parent reply other threads:[~2009-03-17 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 16:26 [PATCH] disable post-checkout test on Cygwin Alex Riesen
2009-03-17 16:52 ` Junio C Hamano
2009-03-17 16:59 ` Johannes Sixt
2009-03-17 20:28 ` Alex Riesen
2009-03-17 20:42 ` Junio C Hamano [this message]
2009-03-17 21:38 ` [PATCH] Define a version of lstat(2) specially for copy operation Alex Riesen
2009-03-18 3:17 ` Mark Levedahl
2009-03-18 7:22 ` Alex Riesen
2009-03-18 7:41 ` Junio C Hamano
2009-03-18 7:56 ` Johannes Sixt
2009-03-18 9:30 ` Junio C Hamano
2009-03-18 10:14 ` Johannes Sixt
2009-03-18 18:56 ` Junio C Hamano
2009-03-17 20:34 ` [PATCH] disable post-checkout test on Cygwin Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v63i7ridk.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=layer@known.net \
--cc=peff@peff.net \
--cc=raa.lkml@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).