mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Wolfgang Walter <wolfgang.walter@studentenwerk.mhn.de>,
	Neil Brown <neilb@suse.de>, Trond Myklebust <trond@netapp.com>,
	stable@kernel.org
Subject: Re: [PATCH] rpc: fix garbage in printk in svc_tcp_accept()
Date: Thu, 20 Sep 2007 13:15:05 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0709201310230.16478@woody.linux-foundation.org> (raw)
In-Reply-To: <20070920195146.GC23287@fieldses.org>



On Thu, 20 Sep 2007, J. Bruce Fields wrote:
>
> we upgraded the kernel of a nfs-server from 2.6.17.11 to 2.6.22.6. Since
> then we get the message
...

Bruce - you're losing authorship information.

Please don't do that.

Put a 

	From: Wolfgang Walter <wolfgang.walter@studentenwerk.mhn.de>

at the top of the email, so that the author gets properly attributed. I 
don't know how many of these I've missed - in this case I just ended up 
googling for the commit message because the "Signed-off-by:" lines implied 
that you weren't the original author, and see the real patch authorship 
that way.

But it's *not* the case that the first sign-off is always the author, and 
I don't want to need to google for each patch I get, so please make it a 
habit to make sure that there's proper attribution for the patches.

Some people (read: Andrew) go so far as to *always* do it (ie Andrew puts 
a "From: Andrew Morton .." at the heads of the emails he sends out), and I 
appreciate it. That way, even if the email then gets forwarded by somebody 
else (because Andrew sent it to some submaintainer instead of me), the 
original authorship doesn't get lost when somebody else then forwards the 
email.

So that "always explicitly say who the author is" is a good idea, but when 
forwarding somebody elses patch, it's *more* than a good idea - at that 
point it's absolutely required for proper attribution.

		Linus

  reply	other threads:[~2007-09-20 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-20 19:51 J. Bruce Fields
2007-09-20 20:15 ` Linus Torvalds [this message]
2007-09-20 20:21   ` J. Bruce Fields

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=alpine.LFD.0.999.0709201310230.16478@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=stable@kernel.org \
    --cc=trond@netapp.com \
    --cc=wolfgang.walter@studentenwerk.mhn.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®