From: Eric Sunshine <sunshine@sunshineco.com>
To: Hariom Verma via GitGitGadget <gitgitgadget@gmail.com>
Cc: Git List <git@vger.kernel.org>, Hariom Verma <hariom18599@gmail.com>
Subject: Re: [PATCH v2 2/2] ref-filter: 'contents:trailers' show error if `:` is missing
Date: Fri, 21 Aug 2020 12:56:56 -0400 [thread overview]
Message-ID: <CAPig+cRxCvHG70Nd00zBxYFuecu6+Z6uDP8ooN3rx9vPagoYBA@mail.gmail.com> (raw)
In-Reply-To: <39aa46bce700cc9a4ca49f38922e3a7ebf14a52c.1598004663.git.gitgitgadget@gmail.com>
On Fri, Aug 21, 2020 at 6:11 AM Hariom Verma via GitGitGadget
<gitgitgadget@gmail.com> wrote:
> The 'contents' atom does not show any error if used with 'trailers'
> atom and semicolon is missing before trailers arguments.
Do you mean s/semicolon/colon/ ?
> e.g %(contents:trailersonly) works, while it shouldn't.
>
> It is definitely not an expected behavior.
>
> Let's fix this bug.
>
> Signed-off-by: Hariom Verma <hariom18599@gmail.com>
> ---
> diff --git a/ref-filter.c b/ref-filter.c
> @@ -332,6 +332,22 @@ static int trailers_atom_parser(const struct ref_format *format, struct used_ato
> +static int check_format_field(const char *arg, const char *field, const char **option)
> +{
> + const char *opt;
> + if (skip_prefix(arg, field, &opt)) {
> + if (*opt == '\0') {
> + *option = NULL;
> + return 1;
> + }
> + else if (*opt == ':') {
> + *option = opt + 1;
> + return 1;
> + }
> + }
> + return 0;
> +}
Not necessarily worth a re-roll, but rather than introducing all the
above new code...
> @@ -345,9 +361,8 @@ static int contents_atom_parser(const struct ref_format *format, struct used_ato
> - else if (skip_prefix(arg, "trailers", &arg)) {
> - skip_prefix(arg, ":", &arg);
> - if (trailers_atom_parser(format, atom, *arg ? arg : NULL, err))
> + else if (check_format_field(arg, "trailers", &arg)) {
> + if (trailers_atom_parser(format, atom, arg, err))
> return -1;
...an alternative would have been something like:
else if (!strcmp(arg, "trailers")) {
if (trailers_atom_parser(format, atom, NULL, err))
return -1;
} else if (skip_prefix(arg, "trailers:", &arg)) {
if (trailers_atom_parser(format, atom, arg, err))
return -1;
}
which is quite simple to reason about (though has the cost of a tiny
bit of duplication).
> diff --git a/t/t6300-for-each-ref.sh b/t/t6300-for-each-ref.sh
> @@ -823,6 +823,15 @@ test_expect_success '%(trailers) rejects unknown trailers arguments' '
> +test_expect_success 'if arguments, %(contents:trailers) shows error if semicolon is missing' '
s/semicolon/colon/
> + # error message cannot be checked under i18n
What is this comment about? I realize that you copied it from other
nearby tests, but I find that it muddies rather than clarifies.
> + cat >expect <<-EOF &&
> + fatal: unrecognized %(contents) argument: trailersonly
> + EOF
> + test_must_fail git for-each-ref --format="%(contents:trailersonly)" 2>actual &&
> + test_i18ncmp expect actual
> +'
next prev parent reply other threads:[~2020-08-21 16:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 12:52 [PATCH 0/2] Fix trailers atom bug and improved tests Hariom Verma via GitGitGadget
2020-08-19 12:52 ` [PATCH 1/2] t6300: unify %(trailers) and %(contents:trailers) tests Hariom Verma via GitGitGadget
2020-08-19 17:31 ` Junio C Hamano
2020-08-21 10:03 ` Hariom verma
2020-08-19 12:52 ` [PATCH 2/2] ref-filter: 'contents:trailers' show error if `:` is missing Hariom Verma via GitGitGadget
2020-08-19 17:55 ` Junio C Hamano
2020-08-19 19:07 ` Junio C Hamano
2020-08-19 19:39 ` Eric Sunshine
2020-08-19 22:08 ` Junio C Hamano
2020-08-20 17:19 ` Hariom verma
2020-08-21 10:11 ` [PATCH v2 0/2] Fix trailers atom bug and improved tests Hariom Verma via GitGitGadget
2020-08-21 10:11 ` [PATCH v2 1/2] t6300: unify %(trailers) and %(contents:trailers) tests Hariom Verma via GitGitGadget
2020-08-21 10:11 ` [PATCH v2 2/2] ref-filter: 'contents:trailers' show error if `:` is missing Hariom Verma via GitGitGadget
2020-08-21 16:56 ` Eric Sunshine [this message]
2020-08-21 19:17 ` Junio C Hamano
2020-08-23 19:25 ` Hariom verma
2020-08-24 3:49 ` Eric Sunshine
2020-08-24 23:32 ` Hariom verma
2020-08-26 6:18 ` Christian Couder
2020-08-26 6:22 ` Christian Couder
2020-08-26 15:18 ` Hariom verma
2020-08-21 21:06 ` [PATCH v3 0/4] [GSoC] Fix trailers atom bug and improved tests Hariom Verma via GitGitGadget
2020-08-21 21:06 ` [PATCH v3 1/4] t6300: unify %(trailers) and %(contents:trailers) tests Hariom Verma via GitGitGadget
2020-08-21 21:06 ` [PATCH v3 2/4] ref-filter: 'contents:trailers' show error if `:` is missing Hariom Verma via GitGitGadget
2020-08-21 21:13 ` Eric Sunshine
2020-08-21 16:19 ` Hariom verma
2020-08-21 21:54 ` Junio C Hamano
2020-08-21 21:06 ` [PATCH v3 3/4] pretty.c: refactor trailer logic to `format_set_trailers_options()` Hariom Verma via GitGitGadget
2020-08-21 21:06 ` [PATCH v3 4/4] ref-filter: using pretty.c logic for trailers Hariom Verma via GitGitGadget
2020-08-21 21:56 ` [PATCH v3 0/4] [GSoC] Fix trailers atom bug and improved tests Junio C Hamano
2020-08-22 14:03 ` Hariom verma
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cRxCvHG70Nd00zBxYFuecu6+Z6uDP8ooN3rx9vPagoYBA@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=hariom18599@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).