From: karthik nayak <karthik.188@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Couder <christian.couder@gmail.com>,
git <git@vger.kernel.org>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Subject: Re: [PATCH v2 09/11] parse-options.h: add macros for '--contains' option
Date: Tue, 16 Jun 2015 02:19:09 +0530 [thread overview]
Message-ID: <CAOLa=ZROvzZD2Qz6gMLeciipJRyAGR5q3isR9zOih9v=GP17EA@mail.gmail.com> (raw)
In-Reply-To: <xmqqbngg93hj.fsf@gitster.dls.corp.google.com>
On Tue, Jun 16, 2015 at 12:57 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Christian Couder <christian.couder@gmail.com> writes:
>
>> The PARSE_OPT_HIDDEN flag is removed below. This means that "--with"
>> will appear in the "git tag -h" output, which means that "--with"
>> should appear in the documentation...
>> The commit message may also want to tell that with is not hidden any more.
>
> Or why is it a good idea to stop hiding.
>
> I would prefer to keep it hidden to avoid "what's the difference
> between the two" confusion.
Ok than, will do that.
--
Regards,
Karthik Nayak
next prev parent reply other threads:[~2015-06-15 20:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 20:17 [PATCH v2 00/11] add options to for-each-ref karthik nayak
2015-06-13 20:18 ` [PATCH v2 01/11] t6301: for-each-ref tests for ref-filter APIs Karthik Nayak
2015-06-13 20:18 ` [PATCH v2 02/11] tag: libify parse_opt_points_at() Karthik Nayak
2015-06-13 20:18 ` [PATCH v2 03/11] ref-filter: implement '--points-at' option Karthik Nayak
2015-06-13 20:18 ` [PATCH v2 04/11] for-each-ref: add " Karthik Nayak
2015-06-13 20:18 ` [PATCH v2 05/11] ref-filter: add parse_opt_merge_filter() Karthik Nayak
2015-06-14 5:49 ` Christian Couder
2015-06-14 6:49 ` karthik nayak
2015-06-13 20:18 ` [PATCH v2 06/11] ref-filter: implement '--merged' and '--no-merged' options Karthik Nayak
2015-06-13 20:18 ` [PATCH v2 07/11] for-each-ref: add " Karthik Nayak
2015-06-13 20:18 ` [PATCH v2 08/11] parse-option: rename parse_opt_with_commit() Karthik Nayak
2015-06-13 20:18 ` [PATCH v2 09/11] parse-options.h: add macros for '--contains' option Karthik Nayak
2015-06-14 6:13 ` Christian Couder
2015-06-14 6:58 ` karthik nayak
2015-06-15 19:27 ` Junio C Hamano
2015-06-15 20:49 ` karthik nayak [this message]
2015-06-13 20:18 ` [PATCH v2 10/11] ref-filter: implement " Karthik Nayak
2015-06-13 20:18 ` [PATCH v2 11/11] for-each-ref: add " Karthik Nayak
2015-06-14 8:12 ` [PATCH v2 01/11] t6301: for-each-ref tests for ref-filter APIs Matthieu Moy
2015-06-14 8:32 ` karthik nayak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOLa=ZROvzZD2Qz6gMLeciipJRyAGR5q3isR9zOih9v=GP17EA@mail.gmail.com' \
--to=karthik.188@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.