git/list[1] front-page[2] threads[3] people[4] search[5] about
wed 2026-10-07 17:16 UTC

git am and duplicate signatures

From
Joe Perches <joe@perches.com>
Date
Aug 30, 2016, 16:12 UTC
Message-ID
<1472573556.5512.93.camel@perches.com>

git-am -s will avoid duplicating the last signature in a patch.

But given a developer creates a patch, send it around for acks/other signoffs, collects signatures and then does a git am -s on a different branch, this sort of sign-off chain is possible:

	Signed-off-by: Original Developer <od@domain.com>
	Acked-by: Random Developer <rd@domain.com>
	Signed-off-by: Original Developer <od@domain.com>

Should there be an option to avoid duplicate signatures in a sequence where an author can git-am the same patch?

sequencer.c:append_signoff() has a flag for APPEND_SIGNOFF_DEDUP
sequencer.c:void append_signoff(struct strbuf *msgbuf, int ignore_footer, unsigned flag)
but
builtin/commit.c:               append_signoff(&sb, ignore_non_trailer(&sb), 0);
doesn't have an optional use mechanism available.
Next: Junio C Hamano
Message 1 of 11 in “git am and duplicate signatures”
  1. Joe PerchesAug 30, 2016
  2. Junio C HamanoAug 30, 2016
  3. Joe PerchesAug 30, 2016
  4. Joe PerchesAug 30, 2016
  5. Junio C HamanoAug 30, 2016
  6. Junio C HamanoAug 30, 2016
  7. Joe PerchesAug 30, 2016
  8. Joe PerchesAug 30, 2016
  9. Junio C HamanoAug 30, 2016
  10. Joe PerchesAug 30, 2016
  11. Junio C HamanoAug 30, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.