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

Re: [PATCH/RFC] remote: support --all for the prune-subcommand

From
Jeff King <peff@peff.net>
Date
Oct 4, 2011, 07:13 UTC
Message-ID
<20111004071332.GA7308@sigill.intra.peff.net>
In-Reply-To
<CABPQNSZrfxhyA3em8TN2=d7pAHopZMgRg47baKnDT9h14=rxkA@mail.gmail.com>
On Tue, Oct 04, 2011 at 09:10:40AM +0200, Erik Faye-Lund wrote:
Show 5 quoted lines
> >  git fetch --all --prune
> >
> I wasn't aware that fetch could prune, but yeah, that seems much
> better to me. Perhaps a mention of this in the "git remote prune"
> documentation could steer other users in the right direction?
Yeah, that makes sense.

There is one slight difference: I think "git remote prune" will _just_ prune, and not fetch into existing refs at all. I'm not sure exactly why you would want that, though. Presumably you run "prune" after you just fetched, anyway. Combining the two steps saves an extra network connection.

-Peff
Previous: Erik Faye-LundNext: Erik Faye-Lund
Message 5 of 10 in “remote: support --all for the prune-subcommand”
  1. remote: support --all for the prune-subcommandErik Faye-Lund, Oct 3, 2011
  2. Jacob HelwigOct 3, 2011
  3. Jeff KingOct 4, 2011
  4. Erik Faye-LundOct 4, 2011
  5. Jeff KingOct 4, 2011
  6. Erik Faye-LundOct 4, 2011
  7. Erik Faye-LundOct 4, 2011
  8. Jeff KingOct 4, 2011
  9. Erik Faye-LundOct 4, 2011
  10. Jeff KingOct 12, 2011

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.