Mark Levedahl <mleved...@gmail.com> writes:
> On 07/21/2013 05:56 PM, Junio C Hamano wrote:
> ...
>> There are only three possible ways going forward, I think:
>>
>> (A) Drop Mark's patch, and do nothing else, because breakages of
>> other people's programs are not fixed by Cygwin 1.7's improved
>> filesystem support, and users still use those mode breaking
>> programs written by others;
>>
>> (B) Drop Mark's patch, and revert c869753e, because it is not the
>> business of our project to sweep breakages of other people's
>> tools under the rug by crippling our software; or
>>
>> (C) Drop NO_TRUSTABLE_FILEMODE for _all_ versions of Cygwin,
>> declaring that the spirit of c869753e to work around bugs in
>> other people's software by crippling Git is justified, but that
>> it is no longer necessary on Cygwin because people do not use
>> such misbehaving third-party tools anymore.
>>
>> These three each rely on its own precondition; I suspect it is
>> likely that (A)'s is the most accurate description of the real world.
>
> Perhaps the simplest approach is to just defer to the judgement of the
> Cygwin project maintainers here.
>
> a) The Cygwin project has its stated objective of being as matching Linux.
That does not say much. On Linux, third-party "native Windows
applications" that necessitated c869753e (Force core.filemode to
false on Cygwin., 2006-12-30) to help users is not an issue. On
Cygwin, it still is.
> b) The Cygwin project has always shipped git binaries built without
> NO_TRUSTABLE_FILEMODE
That is a fair point. So let's do this instead.
-- >8 --
From: Mark Levedahl <mleved...@gmail.com>
Subject: [PATCH] cygwin: stop forcing core.filemode=false
We force core.filemode=false since c869753e (Force core.filemode to
false on Cygwin., 2006-12-30), even when the repository is on a
filesystem on which Cygwin can give us trustable filemodes, because
many native Windows applications the users use to edit files in the
working tree tend to (re)create files with executable bit randomly
set or reset. However, binary distribution of Git that is supplied
by the downstream project to its users has been built without this
consideration.
Drop NO_TRUSTABLE_FILEMODE from our default configuration so that
hand-compiled Git out of box will match theirs.
Signed-off-by: Mark Levedahl <mleved...@gmail.com>
Signed-off-by: Junio C Hamano <gits...@pobox.com>
---
config.mak.uname | 1 -
1 file changed, 1 deletion(-)
diff --git a/config.mak.uname b/config.mak.uname
index 7ac541e..779d06a 100644
--- a/config.mak.uname
+++ b/config.mak.uname
@@ -163,7 +163,6 @@ ifeq ($(uname_O),Cygwin)
NO_THREAD_SAFE_PREAD = YesPlease
NEEDS_LIBICONV = YesPlease
NO_FAST_WORKING_DIRECTORY = UnfortunatelyYes
- NO_TRUSTABLE_FILEMODE = UnfortunatelyYes
NO_ST_BLOCKS_IN_STRUCT_STAT = YesPlease
# There are conflicting reports about this.
# On some boxes NO_MMAP is needed, and not so elsewhere.
--
1.8.3.3-1030-g100bb15
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
