From: Russell King <rmk@arm.linux.org.uk>
To: git@vger.kernel.org
Subject: git-pasky file mode handling
Date: Sat, 16 Apr 2005 10:45:59 +0100 [thread overview]
Message-ID: <20050416104559.A12943@flint.arm.linux.org.uk> (raw)
Hi,
It seems that there's something weird going on with the file mode
handling. Firstly, some files in the git-pasky repository have mode
0664 while others have 0644.
Having pulled from git-pasky a number of times, with Petr's being the
"tracked" repository, I now find that when I do an update-cache --refresh,
it complains that the files need updating, despite show-diff showing no
differences. Investigating, this appears to be because the file modes
are wrong for a number of the files. All my files do not have group
write.
I notice in the changelog what appears to be a dependence on the umask.
If this is so, please note that git appears to track the file modes,
and any dependence upon the umask is likely to screw with this tracking.
--
Russell King
next reply other threads:[~2005-04-16 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 9:45 Russell King [this message]
2005-04-16 14:56 ` git-pasky file mode handling Petr Baudis
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=20050416104559.A12943@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--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