From: Karthik Nayak <karthik.188@gmail.com>
Date: Fri, 18 Sep 2015 15:22:37 GMT
Subject: Re: [PATCH v17 14/14] tag.c: implement '--merged' and '--no-merged' options
Message-ID: <CAOLa=ZRPwoNJv9kG7GfG4ZyjHAoPa7h2PDXErZbV1_B1_ipZ7g@mail.gmail.com>
In-Reply-To: <vpq8u83kb5d.fsf@anie.imag.fr>

On Fri, Sep 18, 2015 at 8:49 PM, Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> Karthik Nayak <karthik.188@gmail.com> writes:
>
>> Not sure this is much of a problem with regards to "--[no-]merged"
>> I mean isn't the square brackets self-explanatory?
>
> Well, usually --no-foo means "cancel the effect of --foo", ie. "git
> command --foo --no-foo" is equivalent to "git command".
>
> Here, --no-merged=some-ref does not _cancel_ the effect but introduce a
> new behavior that was not the default. So it may make sense to explain
> this more clearly.

maybe we should s/no/not ? makes not sense to me

-- 
Regards,
Karthik Nayak