From: Olivier Galibert <galibert@pobox.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Junio C Hamano <junkio@cox.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Shawn O. Pearce" <spearce@spearce.org>,
"Randal L. Schwartz" <merlyn@stonehenge.com>,
James Cloos <cloos@jhcloos.com>,
git@vger.kernel.org, Peter Eriksen <s022018@student.dtu.dk>
Subject: Re: Distribution of longest common hash prefixes
Date: Wed, 4 Apr 2007 01:08:46 +0200 [thread overview]
Message-ID: <20070403230846.GB8479@dspnet.fr.eu.org> (raw)
In-Reply-To: <alpine.LFD.0.98.0704031635100.28181@xanadu.home>
On Tue, Apr 03, 2007 at 04:39:02PM -0400, Nicolas Pitre wrote:
> On Tue, 3 Apr 2007, Junio C Hamano wrote:
>
> > I stated it wrongly. What I was getting at was that we might
> > want to consider an abbreviation that matches only a single
> > commit unambiguous even when there are ambiguous objects of
> > other kinds.
>
> Maybe. But by the time your object hash distribution starts showing
> ambiguous objects with a given abbreviated name between a commit and a
> non commit, I'll bet you'll start to see ambiguities between commits
> soon enough as well.
Isn't the number of objects an order of magnitude bigger than the
number of commits? Well, I guess that depends on your workflow...
OG.
next prev parent reply other threads:[~2007-04-03 23:08 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 [this message]
2007-04-03 23:22 ` Linus Torvalds
2007-04-04 21:03 ` James Cloos
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=20070403230846.GB8479@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=cloos@jhcloos.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=merlyn@stonehenge.com \
--cc=nico@cam.org \
--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 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).