From: Linus Torvalds <torvalds@osdl.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: [GIT PATCH] SCSI updates for 2.6.14
Date: Sat, 5 Nov 2005 11:32:47 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0511051119080.3316@g5.osdl.org> (raw)
In-Reply-To: <1131216913.3614.15.camel@mulgrave>
On Sat, 5 Nov 2005, James Bottomley wrote:
>
> On Sat, 2005-11-05 at 10:42 -0800, Linus Torvalds wrote:
> > James: what's your umask on master? Maybe you've set it to 0077, from the
> > default 0002?
>
> I set it to 0022 ... could that be the problem?
No, 0022 should still be perfectly fine, and should result in drwxr-xr-x,
not your strange things.
Looking at things, I can't imagine it being anything else than a cpio bug
(or misfeature - I don't know where cpio _could_ get the permissions for
the intermediate directories from). But that implies that the system git
shouldn't have mattered, and if you used "git clone -l" with your old git
it should have done exactly the same thing.
Junio: I just confirmed this. Do a
git clone -l src dst
with any git, and you'll end up with
...
drwx------ 2 torvalds torvalds 4096 Nov 5 11:22 de
drwx------ 2 torvalds torvalds 4096 Nov 5 11:22 df
drwx------ 2 torvalds torvalds 4096 Nov 5 11:22 e0
...
drwx------ 2 torvalds torvalds 4096 Nov 5 11:22 ff
drwxrwxr-x 2 torvalds torvalds 4096 Nov 5 11:22 info
drwxrwxr-x 2 torvalds torvalds 4096 Nov 5 11:22 pack
regardless of umask.
Happens with both cpio 2.5 and 2.6.
I _think_ it's this:
...
find objects -type f -print |
cpio -puamd$l "$D/.git/" || exit 1
...
and I suspect that if you remove the "-type f" it will just work (because
it will get the directory permissions from the source). But cpio is black
magic to me (very un-unixy feel to it, I'd guess it comes from some odd
other pre-unix OS).
Linus
parent reply other threads:[~2005-11-05 19:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1131216913.3614.15.camel@mulgrave>]
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.64.0511051119080.3316@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=James.Bottomley@SteelEye.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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