From: James Cloos <cloos@jhcloos.com>
To: git@vger.kernel.org
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
"Randal L. Schwartz" <merlyn@stonehenge.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Eriksen <s022018@student.dtu.dk>
Subject: Re: Distribution of longest common hash prefixes
Date: Wed, 04 Apr 2007 17:03:02 -0400 [thread overview]
Message-ID: <m3bqi3ons2.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0704031046150.6730@woody.linux-foundation.org> (Linus Torvalds's message of "Tue\, 3 Apr 2007 10\:50\:34 -0700 \(PDT\)")
>>>>> "Linus" == Linus Torvalds <torvalds@linux-foundation.org> writes:
Linus> Well, neither of the the two objects at 9 bytes may not be (and
Linus> probably aren't) commits and of the 32 8-nibble cases who knows
Linus> how many are actually commits (probably none), so an 8-byte SHA1
Linus> is *probably* unique at least if you just look at commits.
Linus> Remove the "--objects" to find out.
That makes for:
0:
1:
2: 1
3: 23320
4: 25431
5: 2259
6: 134
7: 8
But is the kernel large enough to be sufficiently representative?
Did Jon complete an import of the 'zilla src?
Has anyone tried to import OOo?
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2007-04-04 21:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 14:58 Distribution of longest common hash prefixes Peter Eriksen
2007-04-02 15:20 ` Linus Torvalds
2007-04-02 16:29 ` Randal L. Schwartz
2007-04-02 17:00 ` Linus Torvalds
2007-04-02 17:17 ` Randal L. Schwartz
2007-04-02 17:33 ` Randal L. Schwartz
2007-04-03 17:04 ` James Cloos
2007-04-03 17:11 ` Randal L. Schwartz
2007-04-03 17:21 ` Shawn O. Pearce
2007-04-03 17:50 ` Linus Torvalds
2007-04-03 18:22 ` Junio C Hamano
2007-04-03 19:27 ` Linus Torvalds
2007-04-03 19:34 ` Nicolas Pitre
2007-04-03 20:25 ` Junio C Hamano
2007-04-03 20:39 ` Nicolas Pitre
2007-04-03 23:08 ` Olivier Galibert
2007-04-03 23:22 ` Linus Torvalds
2007-04-04 21:03 ` James Cloos [this message]
2007-04-02 17:18 ` James Cloos
2007-04-02 15:28 ` Peter Eriksen
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=m3bqi3ons2.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=s022018@student.dtu.dk \
--cc=spearce@spearce.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.