From: Patrick Steinhardt <ps@pks.im>
To: Patrick Monette <pmonette@google.com>
Cc: git@vger.kernel.org, newren@gmail.com, toon@iotcl.com
Subject: Re: [PATCH 2/2] replay: add the -S option
Date: Mon, 28 Sep 2026 09:41:41 +0200 [thread overview]
Message-ID: <aroaNcYqNIXcnQ-L@pks.im> (raw)
In-Reply-To: <20260925205348.1210154-3-pmonette@google.com>
On Fri, Sep 25, 2026 at 04:53:48PM -0400, Patrick Monette wrote:
> diff --git a/builtin/replay.c b/builtin/replay.c
> index d39626a37d..87c628e2ed 100644
> --- a/builtin/replay.c
> +++ b/builtin/replay.c
> @@ -113,6 +113,16 @@ int cmd_replay(int argc,
> PARSE_OPT_NONEG),
> OPT_BOOL(0, "linearize", &opts.linearize,
> N_("drop merge commits, replaying only non-merge commits")),
> + {
> + .type = OPTION_STRING,
> + .short_name = 'S',
> + .long_name = "gpg-sign",
> + .value = &opts.sign_commit,
> + .argh = N_("key-id"),
> + .help = N_("GPG-sign commits"),
> + .flags = PARSE_OPT_OPTARG,
> + .defval = (intptr_t) "",
> + },
> OPT_END()
> };
Okay. We can't use `OPT_STRING()` or `OPT_STRING_F()` here because we
want to set the default value.
I notice that we don't start to honor "commit.gpgSign". Is there a
reason for this?
Patrick
next prev parent reply other threads:[~2026-09-28 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 20:53 [PATCH 0/2] replay: add signing support Patrick Monette
2026-09-25 20:53 ` [PATCH 1/2] replay: handle failure to create commits Patrick Monette
2026-09-28 7:41 ` Patrick Steinhardt
2026-09-25 20:53 ` [PATCH 2/2] replay: add the -S option Patrick Monette
2026-09-28 7:41 ` Patrick Steinhardt [this message]
2026-10-02 21:23 ` Junio C Hamano
2026-09-28 7:41 ` [PATCH 0/2] replay: add signing support Patrick Steinhardt
2026-09-28 15:23 ` Junio C Hamano
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=aroaNcYqNIXcnQ-L@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=pmonette@google.com \
--cc=toon@iotcl.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