From: Junio C Hamano <junkio@cox.net>
To: "Joshua Hudson" <joshudson@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernelsources writeable for everyone?!
Date: Wed, 28 Jun 2006 23:11:55 -0700 [thread overview]
Message-ID: <7v4py4wkwk.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <bda6d13a0606251309x3e07e9feoad777d9a062f923f@mail.gmail.com> (Joshua Hudson's message of "Sun, 25 Jun 2006 13:09:09 -0700")
"Joshua Hudson" <joshudson@gmail.com> writes:
> I feel like asking how they initially get set to world-writable. To me
> it means that the tree that is being tarred up for distribution is
> world-writible. I sure hope that it is a single-user box.
It is _not_ coming from a working tree at all.
git-tar-tree generates the tar image from a git tree object, and
when it does so, it deliberately sets the mode bits to 0666/0777
so that umask of the people who extract the tarball is honored.
In very early days once we made a mistake of generating the tar
archive with more restrictive permission bits (I think it was
0644 or 0755) which was very impolite way to annoy people with
002 umask.
next prev parent reply other threads:[~2006-06-29 6:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 18:00 Daniel
2006-06-24 18:05 ` Avuton Olrich
2006-06-24 18:14 ` Rene Scharfe
2006-06-24 18:17 ` Al Viro
2006-06-25 1:20 ` Mark Rosenstand
2006-06-25 5:38 ` Matthew Frost
2006-06-25 20:09 ` Joshua Hudson
2006-06-25 22:16 ` Matthew Frost
2006-06-25 23:05 ` Matthew Frost
2006-06-29 6:11 ` Junio C Hamano [this message]
2006-06-29 14:38 ` Bill Davidsen
2006-06-26 7:11 ` Troy Benjegerdes
2006-06-26 13:09 ` Rene Scharfe
[not found] <6rkK4-7Do-1@gated-at.bofh.it>
[not found] ` <6rkTT-7OS-23@gated-at.bofh.it>
[not found] ` <6rrsb-vZ-5@gated-at.bofh.it>
[not found] ` <6rvFs-6xp-3@gated-at.bofh.it>
[not found] ` <6rJ5L-1n7-3@gated-at.bofh.it>
[not found] ` <6rL7C-4oS-41@gated-at.bofh.it>
2006-06-25 23:29 ` Bodo Eggert
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=7v4py4wkwk.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=joshudson@gmail.com \
--cc=linux-kernel@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
Powered by JetHome