[PATCH] Documentation: commit: explain the non-meaning of S-o-b

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

 



In the manpage for git commit, the option --signoff is mentioned but
there is no explanation of what it actually means. Add a brief hint that
S-o-b doesn't have a pre-defined meaning.

Signed-off-by: Jan Krüger <jk@xxxxx>
---
Semi-resend. Nobody commented on this when I first sent it in early
December, so here it is again, with a slightly more verbose
explanation. The repetition is intentional.

 Documentation/git-commit.txt |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
index d227cec..cae510b 100644
--- a/Documentation/git-commit.txt
+++ b/Documentation/git-commit.txt
@@ -114,7 +114,10 @@ OPTIONS
 -s::
 --signoff::
 	Add Signed-off-by line by the committer at the end of the commit
-	log message.
+	log message. This line has no inherent meaning; it is up to the
+	potential recipient of the commit to decide what it stands for.
+	It is typically understood as an assurance by the committer that
+	the commit conforms to the receiving project's commit guidelines.
 
 -n::
 --no-verify::
-- 
1.6.5.3.171.ge36e
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[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]