From: Junio C Hamano <gitster@pobox.com>
To: Brandon Richardson <brandon1024.br@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] commit-tree: add missing --gpg-sign flag
Date: Fri, 18 Jan 2019 13:02:02 -0800 [thread overview]
Message-ID: <xmqqy37hiss5.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190118010918.43705-1-brandon1024.br@gmail.com> (Brandon Richardson's message of "Thu, 17 Jan 2019 21:09:18 -0400")
Brandon Richardson <brandon1024.br@gmail.com> writes:
> - if (skip_prefix(arg, "-S", &sign_commit))
> + if(!strcmp(arg, "--gpg-sign")) {
Style. "if (!strcmp(arg, "--gpg-sign")) {"
> + skip_prefix(arg, "--gpg-sign", &sign_commit);
> + continue;
Technically, skipping the prefix S of string S will make us point at
an empty substring at the end. So from that point of view,
skip_prefix(arg, "--gpg-sign", &sign_commit) is not incorrect
per-se, but it is highly misleading. We have already determined
that the user gave us "--gpg-sign" option without anything after it,
so we want to summon the "use the default key" behaviour by giving
an empty string to sign_commit.
An explicit assignment
sign_commit = "";
would be a lot more readable and make the intent a lot more clear.
> + }
> +
> + if (skip_prefix(arg, "-S", &sign_commit) ||
> + skip_prefix(arg, "--gpg-sign=", &sign_commit))
This side is OK. "-S" gives us an empty string, but "-Skeyid" gives
us "keyid" in sign_commit.
> continue;
>
> if (!strcmp(arg, "--no-gpg-sign")) {
> diff --git a/t/t7510-signed-commit.sh b/t/t7510-signed-commit.sh
> index 86d3f93fa..efc136eaf 100755
> --- a/t/t7510-signed-commit.sh
> +++ b/t/t7510-signed-commit.sh
> @@ -51,7 +51,9 @@ test_expect_success GPG 'create signed commits' '
> # commit.gpgsign is still on but this must not be signed
> git tag ninth-unsigned $(echo 9 | git commit-tree HEAD^{tree}) &&
> # explicit -S of course must sign.
> - git tag tenth-signed $(echo 9 | git commit-tree -S HEAD^{tree})
> + git tag tenth-signed $(echo 10 | git commit-tree -S HEAD^{tree})
> + # --gpg-sign must sign.
> + git tag eleventh-signed $(echo 11 | git commit-tree --gpg-sign HEAD^{tree})
> '
>
> test_expect_success GPG 'verify and show signatures' '
prev parent reply other threads:[~2019-01-18 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 1:09 [PATCH] commit-tree: add missing --gpg-sign flag Brandon Richardson
2019-01-18 7:11 ` Martin Ågren
2019-01-18 15:06 ` Brandon Richardson
2019-01-18 21:02 ` Junio C Hamano [this message]
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=xmqqy37hiss5.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=brandon1024.br@gmail.com \
--cc=git@vger.kernel.org \
/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).