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

From: Erik Faye-Lund <kusmabite@gmail.com>
Date: Oct 4, 2011, 07:18 UTC
Message-ID: <CABPQNSZ-ELfFuxmKMqXCQaAgMZMRsZG3S5wWJLsjkYVvK6aGug@mail.gmail.com>
In-Reply-To: <20111004071332.GA7308@sigill.intra.peff.net>

On Tue, Oct 4, 2011 at 9:13 AM, Jeff King <peff@peff.net> wrote:

Show 13 quoted lines

> On Tue, Oct 04, 2011 at 09:10:40AM +0200, Erik Faye-Lund wrote:
>
>> >  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.

Hmm, you might want to do that on, say, a mobile network to save bandwidth; i.e throw away the stale branches, but not yet update the non-stale ones because downloading the objects might take a long time (and/or be expensive).

So with that in mind, I actually think my patch makes sense in some cases, but it certainly is less useful that I originally though ;)

A mention in the documentation seems like a good move no matter what, though.