From: Junio C Hamano <junkio@cox.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Careful object writing..
Date: Tue, 03 May 2005 16:22:53 -0700 [thread overview]
Message-ID: <7vr7gnsxma.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <81b0412b05050316045fa31c2a@mail.gmail.com> (Alex Riesen's message of "Wed, 4 May 2005 01:04:23 +0200")
>>>>> "AR" == Alex Riesen <raa.lkml@gmail.com> writes:
AR> On 5/3/05, Linus Torvalds <torvalds@osdl.org> wrote:
>> I also change the permission to 0444 before it gets its final name.
AR> Maybe umask it first? Just in case.
In general worrying about umask when you see chmod is a good
practice, but it probably is not applicable to this particular
case. A person with umask 077 should still get 0444 if the
SHA1_FILE_DIRECTORY is shared with other people, and if it is
not shared, his initial git-init-db would have made it 0700, so
it does not matter it the files files underneath it have 0444.
next prev parent reply other threads:[~2005-05-03 23:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 19:15 Careful object writing Linus Torvalds
2005-05-03 19:27 ` Chris Wedgwood
2005-05-03 19:47 ` Linus Torvalds
2005-05-03 19:47 ` Chris Wedgwood
2005-05-03 19:56 ` Linus Torvalds
2005-05-03 20:02 ` Daniel Barkalow
2005-05-03 20:00 ` Jan Harkes
2005-05-03 20:11 ` Linus Torvalds
2005-05-03 20:59 ` Jan Harkes
2005-05-03 22:13 ` Linus Torvalds
2005-05-03 22:37 ` Linus Torvalds
2005-05-03 22:40 ` H. Peter Anvin
2005-05-03 23:04 ` Alex Riesen
2005-05-03 23:22 ` Linus Torvalds
2005-05-03 23:25 ` Alex Riesen
2005-05-03 23:22 ` Junio C Hamano [this message]
2005-05-04 4:07 ` [PATCH] Careful object pulling Daniel Barkalow
2005-05-04 9:35 ` Morten Welinder
2005-05-04 16:16 ` Daniel Barkalow
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vr7gnsxma.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).