From: Junio C Hamano <junkio@cox•net>
To: Nicolas Pitre <nico@cam•org>
Cc: Linus Torvalds <torvalds@linux-foundation•org>,
"Shawn O. Pearce" <spearce@spearce•org>,
git@vger•kernel.org
Subject: Re: pack v4 status
Date: Tue, 27 Feb 2007 14:36:05 -0800 [thread overview]
Message-ID: <7vwt23b54a.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <alpine.LRH.0.82.0702271717080.29426@xanadu.home> (Nicolas Pitre's message of "Tue, 27 Feb 2007 17:32:00 -0500 (EST)")
Nicolas Pitre <nico@cam•org> writes:
> On Tue, 27 Feb 2007, Linus Torvalds wrote:
>
>> On Tue, 27 Feb 2007, Shawn O. Pearce wrote:
>> > ...
>> > All trees are then converted to use a 22 byte record format:
>> >
>> > - 2 byte network byte order index into the string pool
>> > - 20 byte SHA-1
>>
>> Umm. Am I missing something, or is this totally braindamaged?
>>
>> Are you really expecting there to never be more than 64k basenames? Trust
>> me, that's a totally broken assumption. Anything that tracks generated
>> stuff will _easily_ have several tens of thousands of random filenames
>> even in a single tree, much less over the whole history of the repository.
>
> The idea is to deal with only tree objects containing the 64K most
> frequently used base names and fall back to the current tree object
> encoding for objects that couldn't be represented that way.
Ah, I was wondering the same thing as Linus after seeing shawn
talked about the 2-byte prefix on #git. Falling back to an
alternate encoding for rarer cases makes sense.
next prev parent reply other threads:[~2007-02-27 22:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 15:50 pack v4 status Shawn O. Pearce
2007-02-27 21:51 ` Linus Torvalds
2007-02-27 22:15 ` Johannes Schindelin
2007-02-27 22:33 ` Nicolas Pitre
2007-02-27 22:32 ` Nicolas Pitre
2007-02-27 22:36 ` Junio C Hamano [this message]
2007-02-28 3:45 ` Shawn O. Pearce
2007-02-28 1:19 ` Nicolas Pitre
2007-02-28 4:13 ` Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2007-02-28 10:04 linux
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=7vwt23b54a.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=nico@cam$(echo .)org \
--cc=spearce@spearce$(echo .)org \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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