From: Junio C Hamano <junkio@cox.net>
To: Nicolas Pitre <nico@cam.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Today's 'master' leaves .idx/.pack in 0400
Date: Sun, 22 Apr 2007 11:52:05 -0700 [thread overview]
Message-ID: <7v3b2snsx6.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <alpine.LFD.0.98.0704221443070.28339@xanadu.home> (Nicolas Pitre's message of "Sun, 22 Apr 2007 14:47:13 -0400 (EDT)")
Nicolas Pitre <nico@cam.org> writes:
> On Sun, 22 Apr 2007, Nicolas Pitre wrote:
>
>> On Sun, 22 Apr 2007, Junio C Hamano wrote:
>>
>> > Nicolas Pitre <nico@cam.org> writes:
>> >
>> > > On Sun, 22 Apr 2007, Junio C Hamano wrote:
>> > >
>> > >> With recent glibc, mkstemp() creates 0400 file. Updated
>> > >> pack-objects uses it in pack/idx writing without fixing this,
>> > >> hence this problem.
>> > >
>> > > Oops. I guess I'm guilty for this. I didn't bother looking at the
>> > > permission on the pack for git-pack-objects since git-repack seemed to
>> > > take care of that. But it only _remove_ write permissions.
>> >
>> > Ok, then probably we can change the 0444 in my "quickfix" patch
>> > to 0644. That should also let the 5300 test pass.
>>
>> Well, actually there is no point making pack files writable. If they're
>> modified, they get corrupted.
>
> OK there are those test cases.
>
> Well... Either we chmod to 0644, or we fix the tests to 'chmod +w' like
> it is already done in t5302.
>
> In any case I wouldn't die() but only error() on a failure to chmod().
> It is sure inconvenient if the pack isn't world readable, but it is not
> a "fatal" problem for the repack.
If it DIED, I would not have to have been embarrassed in public
like this!
Grumble.
next prev parent reply other threads:[~2007-04-22 18:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 2:09 [ANNOUNCE] GIT 1.5.1.1 Junio C Hamano
2007-04-22 6:16 ` [ANNOUNCE] GIT 1.5.1.2 Junio C Hamano
2007-04-22 17:22 ` Linus Torvalds
2007-04-22 17:58 ` Junio C Hamano
2007-04-22 18:06 ` Today's 'master' leaves .idx/.pack in 0400 Junio C Hamano
2007-04-22 18:25 ` Nicolas Pitre
2007-04-22 18:27 ` Junio C Hamano
2007-04-22 18:34 ` Nicolas Pitre
2007-04-22 18:47 ` Nicolas Pitre
2007-04-22 18:52 ` Junio C Hamano [this message]
2007-04-22 18:54 ` Linus Torvalds
2007-04-22 19:03 ` Junio C Hamano
2007-04-22 19:20 ` Junio C Hamano
2007-04-22 19:29 ` Linus Torvalds
2007-04-22 18:47 ` [ANNOUNCE] GIT 1.5.1.2 Junio C Hamano
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=7v3b2snsx6.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.org \
--cc=torvalds@linux-foundation.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 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.