From: "Torsten Bögershausen" <tboegi@web.de>
To: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Git in GSoC 2014 Suggestion: core.filemode always false for cygwin
Date: Wed, 26 Feb 2014 18:15:50 +0100 [thread overview]
Message-ID: <530E2146.1000003@web.de> (raw)
In-Reply-To: <20140225154158.GA9038@sigill.intra.peff.net>
On 2014-02-25 16.41, Jeff King wrote:
> I'm pleased to announce that Git has been accepted to this year's Google
> Summer of Code.
I'm not sure if this is the right way to propose mini projects,
but in case the answer is not no, may I suggest one:
Motivation, the problem:
Since commit c28facd216b501d41ca76f
"cygwin: stop forcing core.filemode=false"
Git under cygwin initializes repos with core.filemode = true under NTFS
This allows a smooth workflow, when e.g. *.sh files are pushed and pulled between
Cygwin, Linux/Unix or Mac OS.
However when I visit such a repo under Mingw, then Mingw reads core.filemode =true,
but is unable to detect whether the X-bit is set, and reads it as not set.
Therefore "git status" thinks that e.g. all *.sh files have lost the executable
bit, abd reports them as changed.
Proposal:
Under Mingw, keep trust_executable_bit always false, regardless what
core.filemode says.
Activate NO_TRUSTABLE_FILEMODE in config.mak.uname for Mingw
(currently it is not used to anything)
Keep the logic in init-db.c to initialize core.filemode = false under Mingw
Language: C
Difficulty: easy
prev parent reply other threads:[~2014-02-26 17:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 15:41 Git in GSoC 2014 Jeff King
2014-02-25 16:42 ` Dmitry S. Dolzhenko
2014-02-25 17:15 ` Michael Haggerty
2014-02-26 10:23 ` Jeff King
2014-02-26 10:41 ` Michael Haggerty
2014-02-26 11:04 ` Jeff King
2014-02-26 11:25 ` Vicent Martí
2014-02-26 11:29 ` Jeff King
2014-02-26 19:48 ` Junio C Hamano
2014-02-27 7:34 ` Michael Haggerty
2014-02-27 19:19 ` Junio C Hamano
2014-02-27 20:26 ` Michael Haggerty
2014-02-27 20:32 ` Junio C Hamano
2014-04-22 1:06 ` Andrew Ardill
2014-04-22 2:18 ` Brian Gesiak
2014-02-26 11:16 ` Duy Nguyen
2014-02-26 11:24 ` Vicent Martí
2014-02-26 11:30 ` Jeff King
2014-02-26 16:48 ` Shawn Pearce
2014-02-26 17:15 ` Torsten Bögershausen [this message]
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=530E2146.1000003@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).