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

Re: [RFC/PATCH 4/4] Re-implement 'git remote update' using 'git fetch'

From
Björn Gustavsson <bgustavsson@gmail.com>
Date
Nov 9, 2009, 06:37 UTC
Message-ID
<6672d0160911082237p4645b8d3n8f667b8fc7c80732@mail.gmail.com>
In-Reply-To
<76718490911081643w46e34858kd82270be0482f8b9@mail.gmail.com>
2009/11/9 Jay Soffian <jaysoffian@gmail.com>:
Show 6 quoted lines
> 2009/11/8 Björn Gustavsson <bgustavsson@gmail.com>:
>> In order to not duplicate functionality, re-implement 'git remote
>> update' in terms of 'git fetch'.
>
> Junio, I guess I'll wait for this to hit pu and then rebase my fetch
> --prune changes on top of it?
It has hit pu now.

If you'll rebase and finish your patch series, I can base my final patch in my series on your changes, because that patch will need a fetch that supports --prune in order to support 'git remote update --prune'.

-- 
Björn Gustavsson, Erlang/OTP, Ericsson AB
Previous: Jay Soffian
Message 5 of 5 in “Re-implement 'git remote update' using 'git fetch'”
  1. 4/4 Re-implement 'git remote update' using 'git fetch'Björn Gustavsson, Nov 8, 2009
  2. Paolo BonziniNov 8, 2009
  3. Björn GustavssonNov 8, 2009
  4. Jay SoffianNov 9, 2009
  5. Björn GustavssonNov 9, 2009

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.