From: Junio C Hamano <gitster@pobox.com>
To: Celeste Liu <coelacanthus@outlook.com>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>,
Raman Gupta <rocketraman@gmail.com>
Subject: Re: [PATCH v3] contrib/rerere-train: avoid useless gpg sign in training
Date: Tue, 19 Jul 2022 11:23:50 -0700 [thread overview]
Message-ID: <xmqqcze1arm1.fsf@gitster.g> (raw)
In-Reply-To: <PH7PR14MB5594A27B9295E95ACA4D6A69CE8F9@PH7PR14MB5594.namprd14.prod.outlook.com> (Celeste Liu's message of "Wed, 20 Jul 2022 01:21:44 +0800")
Celeste Liu <coelacanthus@outlook.com> writes:
> Users may have configured "git merge" to always require GPG
> signing the resulting commits. We are not running "git merge" to
> re-create merge commits, but merely to replay merge conflicts,
> and we will immediately discard the resulting commits; there
> is no point in signing them.
>
> Override such configuration that forces useless signing from the
> command line with the "--no-gpg-sign" option.
>
> Signed-off-by: Celeste Liu <coelacanthus@outlook.com>
> ---
> v2: add problem detail in commit message.
> v3: more detailed reason
Makes sense.
Not a suggestion to change anything, but another possibility may be
to run the command with the --no-commit option, perhaps. If we ever
gained more features added a knob to enable it by default, we would
need to add --no-that-feature as well to refuse it, just like we are
doing so for GPG here, and telling the command that there is no need
to make a commit could turn out to be an easier way to do so for all
extra features that will be invented in the future.
Thanks. Will queue.
>
> contrib/rerere-train.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/contrib/rerere-train.sh b/contrib/rerere-train.sh
> index 26b724c8c6..bd01e430ef 100755
> --- a/contrib/rerere-train.sh
> +++ b/contrib/rerere-train.sh
> @@ -75,7 +75,7 @@ do
> continue
> fi
> git checkout -q "$parent1^0"
> - if git merge $other_parents >/dev/null 2>&1
> + if git merge --no-gpg-sign $other_parents >/dev/null 2>&1
> then
> # Cleanly merges
> continue
prev parent reply other threads:[~2022-07-19 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 17:21 [PATCH v3] contrib/rerere-train: avoid useless gpg sign in training Celeste Liu
2022-07-19 18:23 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqcze1arm1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=coelacanthus@outlook.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=rocketraman@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.