From: Martin Fick <mfick@codeaurora.org>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git@vger.kernel.org
Subject: Re: 66 patches and counting
Date: Thu, 6 Oct 2011 19:59:33 -0600 [thread overview]
Message-ID: <201110061959.34018.mfick@codeaurora.org> (raw)
In-Reply-To: <201110061616.39381.mfick@codeaurora.org>
On Thursday, October 06, 2011 04:16:39 pm Martin Fick wrote:
> On Wednesday, October 05, 2011 03:29:57 pm Michael
> Haggerty
> > [1] hierarchical-refs at
> > git://github.com/mhagger/git.git
>
> I downloaded your patch series and tested it on my repos.
>
> * full fetch changes (> 1 hour) (bad!)
I bisected this problem, it was introduced in this commit:
commit e12ce45b4f1bd8ed6652a742b7e6cf6f101b3604
Author: Michael Haggerty <mhagger@alum.mit.edu>
Date: Wed Oct 5 11:30:06 2011 +0200
Store references hierarchically
This slightly changes the order of iteration over
references; now
references are strictly sorted componentwise rather than
as
"/"-containing strings as before. For example,
"subspace/one" now
sorts before "subspace-x", whereas before the order was
reversed.
Tweak a test case to accept the new ordering.
Up until that point, the fetch looks pretty good,
-Martin
--
Employee of Qualcomm Innovation Center, Inc. which is a
member of Code Aurora Forum
next prev parent reply other threads:[~2011-10-07 1:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 21:29 66 patches and counting Michael Haggerty
2011-10-05 21:36 ` Junio C Hamano
2011-10-05 21:55 ` Jonathan Nieder
2011-10-06 22:16 ` Martin Fick
2011-10-07 1:59 ` Martin Fick [this message]
2011-10-07 3:14 ` Michael Haggerty
2011-10-07 15:51 ` Scalable reference handling Michael Haggerty
2011-10-07 18:51 ` Martin Fick
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=201110061959.34018.mfick@codeaurora.org \
--to=mfick@codeaurora.org \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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.