Re: Would it make sense to add a commit.signOff config?
- From
Johannes Sixt <j6t@kdbg.org>
- Date
- Dec 16, 2025, 07:10 UTC
- Message-ID
- <be069975-8b0f-4915-8c50-0dcbf6efb142@kdbg.org>
- In-Reply-To
- <xmqqwm2n40sf.fsf@gitster.g>
Am 16.12.25 um 03:29 schrieb Junio C Hamano:
Show 28 quoted lines
> Elijah Newren <newren@gmail.com> writes: > >>> 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. >> >> This feels like it's missing context (it'll take the reader a while to >> figure out why the paragraphs are there and that the two are related), > > Very true. It may be sufficient to leave this part unmodified, > keep the updates to gitfaq document, and do nothing else.
Please do leave a pointer here. People who want to automate --signoff do not visit gitfaq, but will search in the command's manual page.
-- Hannes