From: Jeff King <peff@peff.net>
Date: Thu, 02 Apr 2009 13:44:14 GMT
Subject: Re: [PATCH] git remote update: New option --prune (-p)
Message-ID: <20090402134414.GB26699@coredump.intra.peff.net>
In-Reply-To: <9b18b3110904020634i17633645ue4ba91701ea243a1@mail.gmail.com>

On Thu, Apr 02, 2009 at 03:34:15PM +0200, demerphq wrote:

> But one question. It seem to me odd to put this as an option to git
> remote update, and not git remote prune.
> 
> I mean, it seems weird that one must say:
> 
>    git remote update --prune
> 
> and one cannot say:
> 
>    git remote prune --all

But "git remote update" actually respects "remote groups", so it is not
just "--all". I think what you want is "git remote prune <group>".

> especially when there is a `git remote prune` already. It seems a bit
> counterintuitive to find pruning actions under "update", but not all
> that strange to find an all "--all" option for the "prune" action.

I think it makes sense under update as pruning is really just a
different (and perhaps slightly more dangerous) form of update.
Generally I would only want to run prune after having run update, so
combining them makes sense from a workflow perspective.

> Although to me having both be allowed and mean the same thing also
> makes sense.

I think that would make sense, too.

-Peff