Am 8/30/2013 9:32, schrieb Felipe Contreras: > On Fri, Aug 30, 2013 at 2:26 AM, Junio C Hamano <gits...@pobox.com> wrote: >> On Aug 30, 2013 12:19 AM, "Felipe Contreras" <felipe.contre...@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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
