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

Re: Feature Request: `git remote prune --all`

From
Travis Carden <travis.carden@gmail.com>
Date
Aug 18, 2014, 05:56 UTC
Message-ID
<CAByVDedhkUgXkey9dkPYxVQqvzRW4D9OOXt4uFa74+7PvX0mjA@mail.gmail.com>
In-Reply-To
<20140817071805.GC23808@peff.net>

Thanks, guys! `git fetch --all --prune` satisfies my request. I appreciate the education!

On Sun, Aug 17, 2014 at 2:18 AM, Jeff King <peff@peff.net> wrote:
Show 22 quoted lines
> On Sat, Aug 16, 2014 at 07:52:44PM -0500, Travis Carden wrote:
>
>> I would like to propose the addition of a `git remote prune --all`
>> command option or similar mechanism for pruning all remotes in a
>> repository. For lack of such a feature, I've been using the following
>> bash alias:
>>
>> alias git-remote-prune-all='for REMOTE in `git remote`; do echo
>> "Pruning $REMOTE"; git remote prune $REMOTE; done;'
>
> I think in general we've been moving "git remote" away from actually
> interacting with the other side, and pushing those features into "git
> fetch". These days you can use "git fetch --prune --all" to do what you
> want.
>
> Note that this isn't _exactly_ the same thing. Fetch's prune will do a
> normal fetch and _also_ prune. There is no way to say "just prune, but
> do not update existing refs". If that detail is important, I think I'd
> rather see the feature go the other way from your request: teach
> git-fetch a "--prune-only" mode.
>
> -Peff
Previous: Jeff King
Message 3 of 3 in “Feature Request: `git remote prune --all`”
  1. Travis CardenAug 17, 2014
  2. Jeff KingAug 17, 2014
  3. Travis CardenAug 18, 2014

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.