mirror of
https://github.com/git/git.git
synced 2026-01-08 09:13:48 +00:00
Merge branch 'jc/doc-commit-signoff-config'
Documentation update. * jc/doc-commit-signoff-config: signoff-option: linkify the reference to gitfaq commit: document that $command.signoff will not be added
This commit is contained in:
@@ -83,6 +83,25 @@ 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?::
|
||||
Git intentionally does not (and will not) provide a
|
||||
configuration variable, such as `commit.signoff`, to
|
||||
automatically add `--signoff` by default. The reason is to
|
||||
protect the legal and intentional significance of a sign-off.
|
||||
If there were more automated and widely publicized ways for
|
||||
sign-offs to be appended, it would become easier for someone
|
||||
to argue later that a "Signed-off-by" trailer was just added
|
||||
out of habit or by automation, without the committer's full
|
||||
awareness or intent to certify their agreement with the
|
||||
Developer Certificate of Origin (DCO) or a similar statement.
|
||||
This could undermine the sign-off’s credibility in legal or
|
||||
contractual situations.
|
||||
+
|
||||
There exists `format.signoff`, but that is a historical mistake, and
|
||||
it is not an excuse to add more mistakes of the same kind on top.
|
||||
|
||||
|
||||
Credentials
|
||||
-----------
|
||||
|
||||
|
||||
@@ -16,3 +16,7 @@ endif::git-commit[]
|
||||
+
|
||||
The `--no-signoff` option can be used to countermand an earlier `--signoff`
|
||||
option on the command line.
|
||||
+
|
||||
Git does not (and will not) have a configuration variable to enable
|
||||
the `--signoff` command line option by default; see the
|
||||
`commit.signoff` entry in linkgit:gitfaq[7] for more details.
|
||||
|
||||
Reference in New Issue
Block a user