git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Would it make sense to add a commit.signOff config?

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 15, 2025, 01:59 UTC
Message-ID
<xmqqldj48pyl.fsf@gitster.g>
In-Reply-To
<aT9iu9He3yJ3npWX@fruit.crustytoothpaste.net>
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> I think this would be a fine approach or we could add an entry in the
> Git FAQ (or both).  I agree that this is something that comes up
> frequently and writing it down in a more visible way would be kinder to
> users and mailing list participants.
Something like this, then?
---- >8 ----
Subject: [PATCH] document that foo.signoff will not be added

Every now and then we see this coming up on the list. Let's help new contributors who are not aware of past discussions by clearly documenting our past consensus.

Helped-by: brian m. carlson <sandals@crustytoothpaste.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 Documentation/gitfaq.adoc         | 15 +++++++++++++++
 Documentation/signoff-option.adoc | 12 ++++++++++++
 2 files changed, 27 insertions(+)
diff --git c/Documentation/gitfaq.adoc w/Documentation/gitfaq.adoc
index f2917d142c..656093047a 100644
--- c/Documentation/gitfaq.adoc
+++ w/Documentation/gitfaq.adoc
@@ -83,6 +83,21 @@ Windows would be the configuration `"C:\Program Files\Vim\gvim.exe" --nofork`,
 which quotes the filename with spaces and specifies the `--nofork` option to
 avoid backgrounding the process.
 
+[[sign-off]]
+Why not have `commit.signoff` and other configuration variables?::
+	As it makes it harder to argue against one who tells the court
+	"the log message of the commit ends with a Signed-off-by
+	trailer by person X, but it is very plausible that it was done
+	by inertia without person X really intending to certify what
+	DCO says, hence the Signed-off-by trailer is meaningless", if
+	we add more publicized ways to add sign-off automatically, Git
+	does not (and will not) have a configuration variable to
+	enable the `--signoff` command line option it by default.
++
+There exists `format.signoff`, but that is a historical mistake, and
+it is not an excuse to pile on more mistakes of the same kind on top.
+
+
 Credentials
 -----------
 
diff --git c/Documentation/signoff-option.adoc w/Documentation/signoff-option.adoc
index cddfb225d1..0b869dfbe4 100644
--- c/Documentation/signoff-option.adoc
+++ w/Documentation/signoff-option.adoc
@@ -16,3 +16,15 @@ endif::git-commit[]
 +
 The `--no-signoff` option can be used to countermand an earlier `--signoff`
 option on the command line.
++
+As it makes it harder to argue against one who tells the court "the
+log message of the commit ends with a Signed-off-by trailer by person
+X, but it is very plausible that it was done by inertia without person
+X really intending to certify what DCO says, hence the Signed-off-by
+trailer is meaningless", if we add more publicized ways to add
+sign-off automatically, Git does not (and will not) have a
+configuration variable to enable the `--signoff` command line option
+it by default.
++
+There exists `format.signoff`, but that is a historical mistake, and
+it is not an excuse to pile on more mistakes of the same kind on top.
Previous: brian m. carlsonNext: brian m. carlson
Message 6 of 20 in “Would it make sense to add a commit.signOff config?”
  1. Stefan HallerDec 14, 2025
  2. Carlo Marcelo Arenas BelónDec 14, 2025
  3. Junio C HamanoDec 14, 2025
  4. Collin FunkDec 14, 2025
  5. brian m. carlsonDec 15, 2025
  6. Junio C HamanoDec 15, 2025
  7. brian m. carlsonDec 15, 2025
  8. Junio C HamanoDec 16, 2025
  9. Elijah NewrenDec 16, 2025
  10. Junio C HamanoDec 16, 2025
  11. Johannes SixtDec 16, 2025
  12. Johannes SixtDec 16, 2025
  13. commit: document that $command.signoff will not be addedJunio C Hamano, Dec 16, 2025
  14. Elijah NewrenDec 16, 2025
  15. Junio C HamanoDec 17, 2025
  16. Elijah NewrenDec 17, 2025
  17. Johannes SixtDec 17, 2025
  18. Junio C HamanoDec 17, 2025
  19. Kristoffer HaugsbakkDec 19, 2025
  20. Junio C HamanoDec 19, 2025

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.