Re: [PATCH] revision: add --except option
- From
Johannes Sixt <j.sixt@viscovery.net>
- Date
- Aug 30, 2013, 09:08 UTC
- Message-ID
- <5220611C.5080605@viscovery.net>
- In-Reply-To
- <CAMP44s0P=XF5C8+fU2cJ-Xuq57iqcAn674Upub6N=+iiMpQK0g@mail.gmail.com>
Am 8/30/2013 9:32, schrieb Felipe Contreras:
Show 15 quoted lines
> On Fri, Aug 30, 2013 at 2:26 AM, Junio C Hamano <gitster@pobox.com> wrote: >> On Aug 30, 2013 12:19 AM, "Felipe Contreras" <felipe.contreras@gmail.com> >> Would the same argument apply to >> >> next ^maint --except maint >> >> where next gets in the queue, maint in tainted, and skipped? > > maint is not skipped, as it's not the same as ^maint, basically it's > the same as: > > next ^maint > > I think that's good, as there's absolutely no reason why anybody would > want '^maint --except maint' to cancel each other out.
But isn't this basically the same as '--not maint --except maint'? This by itself looks strange. But when disguised in the form '--not --branches --except maint', it would make sense to mean '--not master next', aka '^master ^next'.
-- Hannes