From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: Seeing various mode changes on cygwin
Date: Mon, 10 Oct 2005 00:38:36 -0700 [thread overview]
Message-ID: <7vu0fpbz43.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0510100220330.23242@iabervon.org> (Daniel Barkalow's message of "Mon, 10 Oct 2005 02:48:18 -0400 (EDT)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> Perhaps have a bit in the index mode for the file to say that the mode in
> the filesystem is unreliable, which gets set if a stat of the
> newly-written file doesn't match the mode it was supposed to have, or if
> git chmod is used to change it; then, if the bit is set, ignore the mode
> in the filesystem and just use the mode in the index.
In effect, you are making the "per-repo configuration" Linus
mentioned a non configuration but a property recorded in the
index file. I think this is a clever solution which is very
helpful to the end user. I have to think about this a bit, but
my gut feeling tells me that it is the right direction if it
works.
I do not think you have to necessarily record it in the "index
mode" -- which implies this is per path -- nor even in the index
file itself. We might even be able to get away with doing this
check at git-init-db time just once, and record it in a file,
say ".git/fs-mode-unreliable".
next prev parent reply other threads:[~2005-10-10 7:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 18:00 Seeing various mode changes on cygwin Jonas Fonseca
2005-10-08 18:51 ` Junio C Hamano
2005-10-08 21:36 ` Alex Riesen
2005-10-08 23:36 ` Junio C Hamano
2005-10-09 2:19 ` Linus Torvalds
2005-10-09 6:46 ` Junio C Hamano
2005-10-10 6:48 ` Daniel Barkalow
2005-10-10 7:38 ` Junio C Hamano [this message]
2005-10-10 17:59 ` Daniel Barkalow
2005-10-10 18:22 ` Linus Torvalds
2005-10-10 21:35 ` Add ".git/config" file parser Linus Torvalds
2005-10-10 21:47 ` Linus Torvalds
2005-10-10 21:50 ` H. Peter Anvin
2005-10-10 22:12 ` Linus Torvalds
2005-10-12 0:25 ` Junio C Hamano
2005-10-12 7:43 ` [PATCH] Use core.filemode Junio C Hamano
2005-10-09 3:43 ` Seeing various mode changes on cygwin H. Peter Anvin
2005-10-09 13:02 ` 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=7vu0fpbz43.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
/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).