From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Rene Scharfe <rene.scharfe@lsrfire.ath.cx>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: Honor extractor's umask in git-tar-tree.
Date: Sat, 01 Oct 2005 20:24:12 -0700 [thread overview]
Message-ID: <433F52DC.5090906@zytor.com> (raw)
In-Reply-To: <7vk6gx3vkt.fsf_-_@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> The archive generated with git-tar-tree had 0755 and 0644 mode bits.
> This inconvenienced the extractor with umask 002 by robbing g+w bit
> unconditionally. Just write it out with loose permissions bits and
> let the umask of the extractor do its job.
I've thought that it would be nice if the files/directories were written
into the archive with 0666/0777 permissions by default, and then
extracted with the umask honoured. A special option then could be used
to add files with special permissions, like files in .ssh, which *have*
to be g-w or sshd will reject them.
-hpa
next prev parent reply other threads:[~2005-10-02 3:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 16:03 Destructive side-effect of "cg-status" Wolfgang Denk
2005-10-01 10:24 ` Martin Langhoff
2005-10-01 16:41 ` Linus Torvalds
2005-10-01 18:14 ` Junio C Hamano
2005-10-01 19:07 ` Honor extractor's umask in git-tar-tree Junio C Hamano
2005-10-02 3:24 ` H. Peter Anvin [this message]
2005-10-02 9:55 ` Matthias Urlichs
2005-10-03 4:44 ` H. Peter Anvin
2005-10-03 5:10 ` Junio C Hamano
2005-10-03 16:30 ` H. Peter Anvin
2005-10-03 17:18 ` Junio C Hamano
2005-10-03 17:28 ` H. Peter Anvin
2005-10-03 17:45 ` Linus Torvalds
2005-10-03 18:05 ` H. Peter Anvin
2005-10-03 18:18 ` Linus Torvalds
2005-10-03 18:32 ` H. Peter Anvin
2005-10-01 19:42 ` Destructive side-effect of "cg-status" Wolfgang Denk
2005-10-01 20:24 ` Linus Torvalds
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=433F52DC.5090906@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=rene.scharfe@lsrfire.ath.cx \
--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).