From: "Jan Krüger" <jk@jk.gs>
To: Brent Goodrick <bgoodr@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How can I force git to recognize a change change in file modes?
Date: Sat, 28 Feb 2009 04:55:31 +0100 [thread overview]
Message-ID: <20090228045531.14399ebf@perceptron> (raw)
In-Reply-To: <e38bce640902271717s46cf47f9i7c6bf5aac0d5f273@mail.gmail.com>
Hi,
> I checked in a slew of scripts, only to realize that the file
> permissions were too open (I want them to be chmod 700, not chmod
> 755). Somehow I thought that git was tracking those permission bits,
> but simply using "chmod 700 <fileset>; git add <fileset>" did not add
> the change of file modes, well, at least git status output doesn't
> show it. Is there a way to do this?
git doesn't track permissions quite that closely; all it remembers is
whether the file should be executable or not.
-Jan
next prev parent reply other threads:[~2009-02-28 3:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 1:17 How can I force git to recognize a change change in file modes? Brent Goodrick
2009-02-28 1:25 ` Lars Noschinski
2009-02-28 3:55 ` Jan Krüger [this message]
2009-02-28 16:24 ` Brent Goodrick
2009-02-28 16:52 ` Jay Soffian
2009-02-28 17:34 ` Brent Goodrick
2009-02-28 18:34 ` Todd Zullinger
2009-02-28 22:43 ` Brent Goodrick
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=20090228045531.14399ebf@perceptron \
--to=jk@jk.gs \
--cc=bgoodr@gmail.com \
--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