From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH 0/5] Yet another builtin-fetch round
Date: Wed, 19 Sep 2007 22:09:42 -0700 [thread overview]
Message-ID: <7vsl59ly7d.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7v6426m110.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Wed, 19 Sep 2007 21:08:43 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Daniel Barkalow <barkalow@iabervon.org> writes:
>
>> On Wed, 19 Sep 2007, Shawn O. Pearce wrote:
>>
>>> Another short series for db/fetch-pack, still in pu. Aside from
>>> optimizing the pipeline on the native transport (so we only invoke
>>> the remote process we need once vs. twice) I'm actually now quite
>>> comfortable with this whole series and think it is ready for next.
>>
>> While it's still in pu, should these series of corrections be amended into
>> the original series (for the ones that correct new code)? Most of the
>> before-fixing states aren't worth saving as project history.
>
> Yeah, I was wondering if that is a sane thing to do. It is
> merely additional work to arrive at the same tree state, but
> might be a good investment in the longer term.
Heh, I did not realize that they are now all part of 'next' so
that's moot.
prev parent reply other threads:[~2007-09-20 5:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 4:49 [PATCH 0/5] Yet another builtin-fetch round Shawn O. Pearce
2007-09-20 2:40 ` Daniel Barkalow
2007-09-20 4:08 ` Junio C Hamano
2007-09-20 5:09 ` Junio C Hamano [this message]
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=7vsl59ly7d.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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 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.