git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/5] Yet another builtin-fetch round

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 20, 2007, 04:08 UTC
Message-ID
<7v6426m110.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<Pine.LNX.4.64.0709192233360.21941@iabervon.org>
Daniel Barkalow <barkalow@iabervon.org> writes:
Show 10 quoted lines
> 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.

Previous: Daniel BarkalowNext: Junio C Hamano
Message 3 of 4 in “Yet another builtin-fetch round”
  1. 0/5 Yet another builtin-fetch roundShawn O. Pearce, Sep 19, 2007
  2. Daniel BarkalowSep 20, 2007
  3. Junio C HamanoSep 20, 2007
  4. Junio C HamanoSep 20, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.