From: Chuck Lever <cel@citi.umich.edu>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Catalin Marinas <catalin.marinas@gmail.com>, git@vger.kernel.org
Subject: Re: Diffs "from" working directory
Date: Tue, 22 Nov 2005 13:03:58 -0500 [thread overview]
Message-ID: <43835D8E.60109@citi.umich.edu> (raw)
In-Reply-To: <Pine.LNX.4.64.0511212124160.13959@g5.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
Linus Torvalds wrote:
>
> On Tue, 22 Nov 2005, Chuck Lever wrote:
>
>>for some reason i was under the impression that it would parse the
>>Signed-off-by: fields in the patch description, and take the first one as the
>>patch author.
>
>
> The first sign-off really isn't necessarily the author.
>
> It might be a company sign-off (many companies don't want any random
> engineer to send out patches), but much more commonly it's a trivial patch
> that somebody else signs off on, even if the original patcher didn't (see
> case (b) in the sign-off-rules: you can sign of on somebody elses work if
> you know it's under the GPL).
heh. in fact that is what my company (NetApp) requires.
> So the fact that there was a sign-off procedure doesn't automatically mean
> that the author will be the first sign-off person, although in _practice_
> that obviously would likely always be the most common case by far.
>
> (Another reason is that some people actually add the sign-offs above
> previous ones. It happens, although if I notice, I try to point it out).
>
> So authorship really is totally separate from sign-off, and all _my_ tools
> take the authorship from the first "From:" line at the top of the message
> body or from the email itself.
then perhaps the problem is that the "stg mail" tool should place the
author in the From: field automatically? (ie change the tool, or
permanently modify the default template that comes with StGIT to do
this, as Catalin suggested earlier).
that seems a little twisty to me; you're overloading the SMTP header
field instead of explicitly specifying patch authorship. seems like a
layering violation.
[-- Attachment #2: cel.vcf --]
[-- Type: text/x-vcard, Size: 439 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Charles
org:Network Appliance, Incorporated;Linux NFS Client Development
adr:535 West William Street, Suite 3100;;Center for Information Technology Integration;Ann Arbor;MI;48103-4943;USA
email;internet:cel@citi.umich.edu
title:Member of Technical Staff
tel;work:+1 734 763-4415
tel;fax:+1 734 763 4434
tel;home:+1 734 668-1089
x-mozilla-html:FALSE
url:http://www.monkey.org/~cel/
version:2.1
end:vcard
next prev parent reply other threads:[~2005-11-22 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200511201817.15780.blaisorblade@yahoo.it>
2005-11-20 17:43 ` Diffs "from" working directory J. Bruce Fields
2005-11-20 18:13 ` Linus Torvalds
2005-11-20 20:58 ` J. Bruce Fields
2005-11-21 1:53 ` Chuck Lever
2005-11-21 21:28 ` Catalin Marinas
2005-11-21 21:40 ` Junio C Hamano
2005-11-21 21:45 ` Catalin Marinas
2005-11-22 5:15 ` Chuck Lever
2005-11-22 5:33 ` Linus Torvalds
2005-11-22 18:03 ` Chuck Lever [this message]
2005-11-22 18:32 ` Linus Torvalds
2005-11-22 10:35 ` Catalin Marinas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43835D8E.60109@citi.umich.edu \
--to=cel@citi.umich.edu \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.