Re: [PATCH v2 2/2] sequencer: pass explicit --no-gpg-sign to merge

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Samuel

On 13/10/2020 00:49, Samuel Čavoj wrote:
The merge subcommand launched for merges with non-default strategy would
use its own default behaviour to decide how to sign commits, regardless
of what opts->gpg_sign was set to. For example the --no-gpg-sign flag
given to rebase explicitly would get ignored, if commit.gpgsign was set
to true.

That's a good explanation, thanks very much for adding this patch

Phillip


Signed-off-by: Samuel Čavoj <samuel@xxxxxxxxx>
---
  sequencer.c | 2 ++
  1 file changed, 2 insertions(+)

diff --git a/sequencer.c b/sequencer.c
index 88ccff4838..043d606829 100644
--- a/sequencer.c
+++ b/sequencer.c
@@ -3678,6 +3678,8 @@ static int do_merge(struct repository *r,
  		strvec_push(&cmd.args, git_path_merge_msg(r));
  		if (opts->gpg_sign)
  			strvec_pushf(&cmd.args, "-S%s", opts->gpg_sign);
+		else
+			strvec_push(&cmd.args, "--no-gpg-sign");
/* Add the tips to be merged */
  		for (j = to_merge; j; j = j->next)





[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux