* [PATCH] Documentation: commit: explain the non-meaning of S-o-b
@ 2009-12-01 22:25 Jan Krüger
0 siblings, 0 replies; 3+ messages in thread
From: Jan Krüger @ 2009-12-01 22:25 UTC (permalink / raw)
To: Git ML
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@jk.gs>
---
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
@@ -100,7 +100,8 @@ 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; what it stands for
+ is up to whoever includes this commit in a repository.
-n::
--no-verify::
--
1.6.5.3.171.ge36e
^ permalink raw reply related [flat|nested] 3+ messages in thread
* [PATCH] Documentation: commit: explain the non-meaning of S-o-b
@ 2009-12-28 18:40 Jan Krüger
2009-12-29 7:54 ` Junio C Hamano
0 siblings, 1 reply; 3+ messages in thread
From: Jan Krüger @ 2009-12-28 18:40 UTC (permalink / raw)
To: Junio C Hamano; +Cc: Git ML
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@jk.gs>
---
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
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] Documentation: commit: explain the non-meaning of S-o-b
2009-12-28 18:40 [PATCH] Documentation: commit: explain the non-meaning of S-o-b Jan Krüger
@ 2009-12-29 7:54 ` Junio C Hamano
0 siblings, 0 replies; 3+ messages in thread
From: Junio C Hamano @ 2009-12-29 7:54 UTC (permalink / raw)
To: Jan Krüger; +Cc: Git ML
Jan Krüger <jk@jk.gs> writes:
> 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.
The commands am, cherry-pick, commit, format-patch, and revert all share
the "sign-off" and they more or less deliberately refused to define what
it means to sign-off a patch; as your patch says, it is up to the project
policy.
config.txt gives a description for format.signoff option that is too
specific to git and the kernel, which I think is a mistake given the much
wider audience we have these days.
How similar should the document for the "sign-off" options to these
commands be? I am wondering if we should have the same description copied
and pasted to all of them, or avoid repeating ourselves and instead have
them refer to a central place, perhaps somewhere in the Tutorial or the
Workflow document.
> Signed-off-by: Jan Krüger <jk@jk.gs>
> ---
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-12-29 7:54 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-28 18:40 [PATCH] Documentation: commit: explain the non-meaning of S-o-b Jan Krüger
2009-12-29 7:54 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2009-12-01 22:25 Jan Krüger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).