From: Junio C Hamano <gitster@pobox.com>
To: Joe Perches <joe@perches.com>
Cc: git@vger.kernel.org, jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH] git-send-email: Add auto-cc to all body signatures
Date: Thu, 08 Dec 2011 11:37:07 -0800 [thread overview]
Message-ID: <7v8vmmj1ng.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1323313119.1762.58.camel@joe2Laptop> (Joe Perches's message of "Wed, 07 Dec 2011 18:58:39 -0800")
Joe Perches <joe@perches.com> writes:
> Many types of signatures are used by various projects.
>
> The most common type is formatted:
> "[some_signature_type]-by: First Last <email@domain.tld>"
> e.g:
> "Reported-by: First Last <email@domain.tld>" (no quotes are used)
This is just a phrasing issue, but I am a bit reluctant about the name
"signature". "Acked-by:", "Tested-by:" and "Reviewed-by:" are originally
written in the message sent to the author by the person who is giving an
Ack, a successful test report, and a review comment, and the author (at
least in spirit) copies & pastes them to the final text used in the commit
log message, so it would not be incorrect to call them "signatures". But
other "Random-by:" would not fall into that pattern.
"Reported-by:" certainly does not. It is almost always added by the
author of the patch that is different from the reporter, and the reporter
wouldn't have written "Reported-by: me" in the original bug report that
triggered the discussion and resulted in the commit to fix the bug. Such a
line is certainly not a signature of/by the reporter. Same can be said for
"Helped-by:" for the author to share credits.
Also I've seen these "Random-by:", especially the ones that the author
adds on his own initiative like "Reported-by:", followed by just a name
but not an addresses [*1*].
Does your change do the right thing on such an address-less entry? The
answer to this question must start with the definition of "the right thing
to do is X", of course.
> diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
> index 327233c..17ea825 100644
> --- a/Documentation/git-send-email.txt
> +++ b/Documentation/git-send-email.txt
> @@ -246,8 +246,9 @@ Automating
> patch body (commit message) except for self (use 'self' for that).
> - 'sob' will avoid including anyone mentioned in Signed-off-by lines except
> for self (use 'self' for that).
> +- 'signatures' will avoid including anyone mentioned in any "<foo>-by:" lines.
> - 'cccmd' will avoid running the --cc-cmd.
> -- 'body' is equivalent to 'sob' + 'bodycc'
> +- 'body' is equivalent to 'sob' + 'bodycc + signatures'
The quotes do not match quite well.
[Footnote]
*1* This seems to be done deliberately so; I understand that this is to
avoid running afoul of EU privacy legislation or something.
next prev parent reply other threads:[~2011-12-08 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 1:34 [PATCH] git-send-email: Add auto-cc to all body signatures Joe Perches
2011-07-29 1:43 ` Jeff Kirsher
2011-12-08 2:58 ` Joe Perches
2011-12-08 19:37 ` Junio C Hamano [this message]
2011-12-08 20:51 ` Joe Perches
2015-12-02 10:04 ` Rasmus Villemoes
2015-12-02 17:00 ` [PATCH V3] " Joe Perches
2015-12-02 17:58 ` Junio C Hamano
2015-12-02 18:20 ` Joe Perches
2015-12-02 18:28 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v8vmmj1ng.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=joe@perches.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).