From: Nicolas Pitre <nico@cam.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [Junio C Hamano] Re: Consolidate SHA1 object file close
Date: Sun, 15 Jun 2008 21:13:41 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0806152108410.23110@xanadu.home> (raw)
In-Reply-To: <alpine.LFD.1.10.0806151057100.2949@woody.linux-foundation.org>
On Sun, 15 Jun 2008, Linus Torvalds wrote:
>
>
> On Sat, 14 Jun 2008, Junio C Hamano wrote:
> >
> > Other than that I had to stop for a few seconds to think at the magic
> > "20 bytes longer", they look scary-but-correct ;-).
BTW, isn't the same concerns valid for temporary pack file creation too?
Or maybe we just don't care in the context of packs?
Also... this change is lacking its counterpart in
builtin-prune.c:remove_temporary_files().
Nicolas
next prev parent reply other threads:[~2008-06-16 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 22:42 [Junio C Hamano] Re: Consolidate SHA1 object file close Junio C Hamano
2008-06-15 18:08 ` Linus Torvalds
2008-06-16 1:13 ` Nicolas Pitre [this message]
2008-06-17 5:01 ` Junio C Hamano
2008-06-17 16:30 ` Linus Torvalds
2008-07-04 17:44 ` Pierre Habouzit
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=alpine.LFD.1.10.0806152108410.23110@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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).