From: "Martin Ågren" <martin.agren@gmail.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Use OPT_SET_INT_F() for cmdline option specification
Date: Sun, 20 May 2018 11:15:58 +0200 [thread overview]
Message-ID: <CAN0heSpdtiUVSYGsT+VnUaSy0BO+p+mnod6Ut4Y3UrNVVQkrbA@mail.gmail.com> (raw)
In-Reply-To: <20180520081244.14619-1-pclouds@gmail.com>
On 20 May 2018 at 10:12, Nguyễn Thái Ngọc Duy <pclouds@gmail.com> wrote:
> The only thing these commands need is extra parseopt flags which can be
> passed in by OPT_SET_INT_F() and it is a bit more compact than full
> struct initialization.
> diff --git a/archive.c b/archive.c
> index 93ab175b0b..4fe7bec60c 100644
> --- a/archive.c
> +++ b/archive.c
> @@ -411,11 +411,9 @@ static void parse_treeish_arg(const char **argv,
> }
>
> #define OPT__COMPR(s, v, h, p) \
> - { OPTION_SET_INT, (s), NULL, (v), NULL, (h), \
> - PARSE_OPT_NOARG | PARSE_OPT_NONEG, NULL, (p) }
> + OPT_SET_INT_F(s, NULL, v, h, p, PARSE_OPT_NONEG)
> #define OPT__COMPR_HIDDEN(s, v, p) \
> - { OPTION_SET_INT, (s), NULL, (v), NULL, "", \
> - PARSE_OPT_NOARG | PARSE_OPT_NONEG | PARSE_OPT_HIDDEN, NULL, (p) }
> + OPT_SET_INT_F(s, NULL, v, "", p, PARSE_OPT_NONEG | PARSE_OPT_HIDDEN)
Right. We have NULLs in the fifth and the second-to-last positions, and
we use PARSE_OPT_NOARG. By switching to OPT_SET_INT_F we get those for
free.
Do we want to keep "(s)" instead of "s", just to be safe? And same for
"(v)", "(p)". Macro expansion always makes me paranoid.
> diff --git a/builtin/am.c b/builtin/am.c
> index d834f9e62b..666287b497 100644
> --- a/builtin/am.c
> +++ b/builtin/am.c
> @@ -2231,12 +2231,12 @@ int cmd_am(int argc, const char **argv, const char *prefix)
> N_("pass -b flag to git-mailinfo"), KEEP_NON_PATCH),
> OPT_BOOL('m', "message-id", &state.message_id,
> N_("pass -m flag to git-mailinfo")),
> - { OPTION_SET_INT, 0, "keep-cr", &keep_cr, NULL,
> - N_("pass --keep-cr flag to git-mailsplit for mbox format"),
> - PARSE_OPT_NOARG | PARSE_OPT_NONEG, NULL, 1},
> - { OPTION_SET_INT, 0, "no-keep-cr", &keep_cr, NULL,
> - N_("do not pass --keep-cr flag to git-mailsplit independent of am.keepcr"),
> - PARSE_OPT_NOARG | PARSE_OPT_NONEG, NULL, 0},
> + OPT_SET_INT_F(0, "keep-cr", &keep_cr,
> + N_("pass --keep-cr flag to git-mailsplit for mbox format"),
> + 1, PARSE_OPT_NONEG),
> + OPT_SET_INT_F(0, "no-keep-cr", &keep_cr,
> + N_("do not pass --keep-cr flag to git-mailsplit for mbox format"),
> + 0, PARSE_OPT_NONEG),
I found `-w` and `--word-diff` useful. You actually change the N_("...")
for `--no-keep-cr` here: [-independent of am.keepcr-]{+for mbox format+}
Copy-paste mistake?
Other than that, `--word-diff` has a very structured appearance and
nothing stood out. The ordering is different (f goes at the end in the
post-image), which makes the diff busier than it would have had to be.
(That's obviously nothing this patch can do anything about.)
Martin
next prev parent reply other threads:[~2018-05-20 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-20 8:12 [PATCH] Use OPT_SET_INT_F() for cmdline option specification Nguyễn Thái Ngọc Duy
2018-05-20 9:15 ` Martin Ågren [this message]
2018-05-20 15:40 ` Duy Nguyen
2018-05-20 15:42 ` [PATCH v2] " Nguyễn Thái Ngọc Duy
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=CAN0heSpdtiUVSYGsT+VnUaSy0BO+p+mnod6Ut4Y3UrNVVQkrbA@mail.gmail.com \
--to=martin.agren@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@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).