From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: [PATCH 3/4] Make git-fetch follow tags we already have objects for sooner
Date: Fri, 29 Feb 2008 17:34:31 -0500 [thread overview]
Message-ID: <20080229223431.GT8410@spearce.org> (raw)
In-Reply-To: <7v3arcduil.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> wrote:
> This is cute. Obviously some tests need to be adjusted for this
> change, though.
I'll take a look at the current tests this weekend and see what
needs to be adjusted, if anything. I'd also like to get a few
tests written for this, so we are certain the optimizations are
kicking in when they are supposed to be.
--
Shawn.
next prev parent reply other threads:[~2008-02-29 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 8:42 [PATCH 3/4] Make git-fetch follow tags we already have objects for sooner Shawn O. Pearce
2008-02-29 8:41 ` Junio C Hamano
2008-02-29 22:34 ` Shawn O. Pearce [this message]
2008-02-29 22:39 ` Daniel Barkalow
2008-03-01 4:25 ` Shawn O. Pearce
2008-03-01 16:33 ` Daniel Barkalow
2008-03-02 14:13 ` Shawn O. Pearce
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=20080229223431.GT8410@spearce.org \
--to=spearce@spearce.org \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).