git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, Alex Riesen <raa.lkml@gmail.com>,
	git@vger.kernel.org
Subject: Re: Seeing various mode changes on cygwin
Date: Mon, 10 Oct 2005 02:48:18 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.63.0510100220330.23242@iabervon.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0510081909250.31407@g5.osdl.org>

On Sat, 8 Oct 2005, Linus Torvalds wrote:

> I think we might want to have a flag that says "don't care about 
> filesystem modes". That should be pretty easy, I think we'd get most of 
> them by just adding some logic to "ce_match_stat()".
> 
> Then add a "git chmod" to set the mode in the index (which should end up 
> being just a wrapper around the regular "git-update-index" using the 
> "--cacheinfo" flag, I think).
> 
> Those parts should be trivial.
> 
> The more interesting issue is how to set the _flag_ that we should do 
> this. We may have to add a config file, and it should be per-repository 
> (ie something like ".git/config" or ".git/info/config"). Or do we just do 
> yet another environment variable?

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.

This should prevent modes from magically changing, even if the user 
doesn't do anything special.

	-Daniel
*This .sig left intentionally blank*

  parent reply	other threads:[~2005-10-10  6:43 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 [this message]
2005-10-10  7:38           ` Junio C Hamano
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=Pine.LNX.4.63.0510100220330.23242@iabervon.org \
    --to=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=raa.lkml@gmail.com \
    --cc=torvalds@osdl.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).