From: "Bryan O'Sullivan" <bryano@fb.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: logging disjoint sets of commits in a single command
Date: Wed, 1 Feb 2012 22:01:52 +0000 [thread overview]
Message-ID: <CB4EF5E8.7A0%bryano@fb.com> (raw)
In-Reply-To: <20120201030300.GA9969@sigill.intra.peff.net>
On 2012-01-31 19:03 , "Jeff King" <peff@peff.net> wrote:
>
>That sounds kind of slow. Is your repository really gigantic?
Bigger than a kernel tree, but not as many commits. Beyond that, can't say.
> Have you packed
>everything?
Yep.
> I'm just curious if there's some other way to make things
>faster.
It would be nice if there was, but the fundamental problem is the lack of
an index from filename to commit. Walking every commit is the limiting
factor, I believe.
> Is the repository publicly available?
No, sorry.
next prev parent reply other threads:[~2012-02-01 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 0:15 logging disjoint sets of commits in a single command Bryan O'Sullivan
2012-02-01 0:27 ` Bryan O'Sullivan
2012-02-01 0:39 ` Carlos Martín Nieto
2012-02-01 0:53 ` Jeff King
2012-02-01 1:02 ` Bryan O'Sullivan
2012-02-01 3:03 ` Jeff King
2012-02-01 22:01 ` Bryan O'Sullivan [this message]
2012-02-01 0:48 ` Junio C Hamano
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=CB4EF5E8.7A0%bryano@fb.com \
--to=bryano@fb.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).