From: "H. Peter Anvin" <hpa@zytor.com>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: git@vger.kernel.org
Subject: Re: Honor extractor's umask in git-tar-tree.
Date: Sun, 02 Oct 2005 21:44:43 -0700 [thread overview]
Message-ID: <4340B73B.1090409@zytor.com> (raw)
In-Reply-To: <pan.2005.10.02.09.55.52.564046@smurf.noris.de>
Matthias Urlichs wrote:
> Hi, H. Peter Anvin wrote:
>
>>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.
>
> The git archive oesn't *have* permissions, just one "execute" bit.
>
My point is that I believe it should. It has the bitfield for it, it
just doesn't use it at the moment.
>> 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.
>
> I'd include a script in the archive which you'd run afterwards to fix
> problems like this. IMHO, in most situations you'll need it anyway
> (for instance, to re-start services).
That is true in some cases, but I highly disagree with the statement "most".
-hpa
next prev parent reply other threads:[~2005-10-03 4:46 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
2005-10-02 9:55 ` Matthias Urlichs
2005-10-03 4:44 ` H. Peter Anvin [this message]
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=4340B73B.1090409@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=smurf@smurf.noris.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.