From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com>,
nsengaw4c via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] ref-filter: add new atom "signature" atom
Date: Tue, 03 Jan 2023 09:58:02 +0900 [thread overview]
Message-ID: <xmqqv8lov3hh.fsf@gitster.g> (raw)
In-Reply-To: CAP8UFD3i7C2c79V2ORxh-Q-rNuwKVqkMRX0VoXy3iugw=u5K+A@mail.gmail.com
Christian Couder <christian.couder@gmail.com> writes:
>> I am not sure I have understood this, which helper?
>
> I think Junio is talking about the following function:
>
> static enum signature_option parse_signature_option(const char *arg)
>
> he suggested above.
Correct.
> With this function the above code could be just something like:
>
> if (parse_signature_option(name) < 0)
> continue;
More or less so, but the first "if" in the helper I wrote in the
message above is broken. It should be
static enum signature_option parse_signature_option(const char *arg)
{
if (!*arg)
return S_BARE;
else if (!strcmp(arg, "signer"))
return S_SIGNER;
...
else
return -1;
}
and then the code equivalent to the bunch of strcmp() would be
if (skip_prefix(name, "signature", &name) &&
(!*name || *name++ == ':') &&
(0 <= parse_signature_option(name)))
; /* we have "signature"-related atom */
else
continue; /* not a "signature" atom */
or something like that.
next prev parent reply other threads:[~2023-01-03 0:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 0:55 [PATCH] ref-filter: add new atom "signature" atom nsengaw4c via GitGitGadget
2022-12-27 2:20 ` Junio C Hamano
2023-01-02 4:49 ` NSENGIYUMVA WILBERFORCE
2023-01-02 8:37 ` Christian Couder
2023-01-03 0:58 ` Junio C Hamano [this message]
[not found] ` <CA+PPyiGd0-AiwhPa5e+fDdA9RybS+c5XeOYm5yycCZco3VHAxg@mail.gmail.com>
2023-01-08 15:21 ` NSENGIYUMVA WILBERFORCE
2022-12-27 6:11 ` Jeff King
2023-01-02 6:34 ` NSENGIYUMVA WILBERFORCE
2023-01-10 0:52 ` [PATCH v3 0/1] ref-filter: add new " Nsengiyumva Wilberforce
2023-01-10 0:52 ` [PATCH v3 1/1] " Nsengiyumva Wilberforce
2023-01-16 17:38 ` [PATCH v4 0/1] " Nsengiyumva Wilberforce
2023-01-16 17:38 ` [PATCH v4 1/1] " Nsengiyumva Wilberforce
2023-03-11 21:06 ` [PATCH v5 0/1] " Nsengiyumva Wilberforce
2023-03-11 21:06 ` [PATCH v5 1/1] " Nsengiyumva Wilberforce
2023-03-14 22:51 ` Junio C Hamano
2023-04-28 18:29 ` Kousik Sanagavarapu
2023-04-29 18:37 ` Kousik Sanagavarapu
2023-01-26 21:07 ` [PATCH v4 0/1] " Junio C Hamano
2023-01-10 9:13 ` [PATCH v3 " Christian Couder
-- strict thread matches above, loose matches on Subject: below --
2023-01-09 9:02 [PATCH] ref-filter: add new atom " nsengaw4c via GitGitGadget
2023-01-09 9:45 ` Christian Couder
2023-01-09 12:59 ` NSENGIYUMVA WILBERFORCE
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=xmqqv8lov3hh.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=nsengiyumvawilberforce@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).