From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: Re: [PATCH] cogito: Avoid slowness when timewarping large trees.
Date: Sat, 25 Mar 2006 04:36:41 -0500 [thread overview]
Message-ID: <20060325093641.GA26284@coredump.intra.peff.net> (raw)
In-Reply-To: <20060324164352.GA20684@spearce.org>
On Fri, Mar 24, 2006 at 11:43:52AM -0500, Shawn Pearce wrote:
> Now that I think about it isn't this sort of where you were before
> in cg-seek?
Yes, that's basically it. Short of Junio explaining how the manual file
removal can be avoided, I think my original patch should be applied, as
it causes an order of magnitude speed up. I will repost the cleaned-up
version.
-Peff
next prev parent reply other threads:[~2006-03-25 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 8:44 [PATCH] cogito: Avoid slowness when timewarping large trees Jeff King
2006-03-24 10:21 ` Junio C Hamano
2006-03-24 10:55 ` Jeff King
2006-03-24 11:01 ` Junio C Hamano
2006-03-24 11:22 ` Jeff King
2006-03-24 16:43 ` Shawn Pearce
2006-03-25 9:36 ` Jeff King [this message]
2006-03-25 9:39 ` [PATCH] " Jeff King
2006-03-26 18:05 ` Petr Baudis
2006-03-25 19:55 ` [PATCH] cogito: " 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=20060325093641.GA26284@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.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).