From: Christian Couder <christian.couder@gmail.com>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: 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: Sun, 14 Jun 2015 08:13:07 +0200 [thread overview]
Message-ID: <CAP8UFD02qxKJYJ=hg7ZWsvUZfJe85CY-v2V-64swdxnibF=mmg@mail.gmail.com> (raw)
In-Reply-To: <1434226706-3764-9-git-send-email-karthik.188@gmail.com>
On Sat, Jun 13, 2015 at 10:18 PM, Karthik Nayak <karthik.188@gmail.com> wrote:
> Add a macro for using the '--contains' option in parse-options.h
> also include an optional '--with' option macro which performs the
> same action as '--contains'.
>
> Make tag.c use this new macro
>
> Mentored-by: Christian Couder <christian.couder@gmail.com>
> Mentored-by: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
> Signed-off-by: Karthik Nayak <karthik.188@gmail.com>
> ---
> builtin/tag.c | 14 ++------------
> parse-options.h | 7 +++++++
> 2 files changed, 9 insertions(+), 12 deletions(-)
>
> diff --git a/builtin/tag.c b/builtin/tag.c
> index 2d6610a..767162e 100644
> --- a/builtin/tag.c
> +++ b/builtin/tag.c
> @@ -595,23 +595,13 @@ int cmd_tag(int argc, const char **argv, const char *prefix)
>
> OPT_GROUP(N_("Tag listing options")),
> OPT_COLUMN(0, "column", &colopts, N_("show tag list in columns")),
> + OPT_CONTAINS(&with_commit, N_("print only tags that contain the commit")),
> + OPT_WITH(&with_commit, N_("print only tags that contain the commit")),
> {
> OPTION_CALLBACK, 0, "sort", &tag_sort, N_("type"), N_("sort tags"),
> PARSE_OPT_NONEG, parse_opt_sort
> },
> {
> - OPTION_CALLBACK, 0, "contains", &with_commit, N_("commit"),
> - N_("print only tags that contain the commit"),
> - PARSE_OPT_LASTARG_DEFAULT,
> - parse_opt_commit_object_name, (intptr_t)"HEAD",
> - },
> - {
> - OPTION_CALLBACK, 0, "with", &with_commit, N_("commit"),
> - N_("print only tags that contain the commit"),
> - PARSE_OPT_HIDDEN | PARSE_OPT_LASTARG_DEFAULT,
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.
> - parse_opt_commit_object_name, (intptr_t)"HEAD",
> - },
> - {
> OPTION_CALLBACK, 0, "points-at", &points_at, N_("object"),
> N_("print only tags of the object"), 0, parse_opt_object_name
> },
> diff --git a/parse-options.h b/parse-options.h
> index 8542d9c..d76e907 100644
> --- a/parse-options.h
> +++ b/parse-options.h
> @@ -243,5 +243,12 @@ extern int parse_opt_noop_cb(const struct option *, const char *, int);
> OPT_COLOR_FLAG(0, "color", (var), (h))
> #define OPT_COLUMN(s, l, v, h) \
> { OPTION_CALLBACK, (s), (l), (v), N_("style"), (h), PARSE_OPT_OPTARG, parseopt_column_callback }
> +#define _OPT_CONTAINS_OR_WITH(name, variable, help) \
> + { OPTION_CALLBACK, 0, name, (variable), N_("commit"), (help), \
> + PARSE_OPT_LASTARG_DEFAULT, \
> + parse_opt_commit_object_name, (intptr_t) "HEAD" \
> + }
> +#define OPT_CONTAINS(v, h) _OPT_CONTAINS_OR_WITH("contains", v, h)
> +#define OPT_WITH(v, h) _OPT_CONTAINS_OR_WITH("contains", v, h)
Shouldn't it be "with" instead of "contains"?
next prev parent reply other threads:[~2015-06-14 6:13 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 [this message]
2015-06-14 6:58 ` karthik nayak
2015-06-15 19:27 ` Junio C Hamano
2015-06-15 20:49 ` karthik nayak
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='CAP8UFD02qxKJYJ=hg7ZWsvUZfJe85CY-v2V-64swdxnibF=mmg@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).