From: Paul Mackerras <paulus@samba.org>
To: "K.Prasad" <prasad@linux.vnet.ibm.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Benjamin Herrenschmidt <benh@au1.ibm.com>
Subject: Re: [Patch 0/5] PPC64-HWBKPT: Hardware Breakpoint interfaces - ver XXII
Date: Thu, 10 Jun 2010 14:23:51 +1000 [thread overview]
Message-ID: <20100610042351.GA17989@drongo> (raw)
In-Reply-To: <20100609103223.GA10656@in.ibm.com>
On Wed, Jun 09, 2010 at 04:02:23PM +0530, K.Prasad wrote:
> (Given that it's your idea I've added your
> signed-off too).
Actually, you should never add someone else's signed-off-by unless
they specifically ask you to. The signed-off-by lines are supposed to
show the path that the patch took to get into the tree, so in general
only the original author(s) and the maintainers who passed the patch
along should add signed-off-by lines. It would only be a maintainer
who would add someone else's signed-off-by, and then only if someone
who needs to sign off on the patch had forgotten and then asked the
maintainer to correct their mistake.
In this case the appropriate way to give credit would be just a
sentence in the patch description; no formal tag is needed.
Paul.
next prev parent reply other threads:[~2010-06-10 4:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 6:39 [Patch 0/5] PPC64-HWBKPT: Hardware Breakpoint interfaces - ver XXII K.Prasad
2010-06-02 11:33 ` Paul Mackerras
2010-06-04 6:51 ` K.Prasad
2010-06-04 9:06 ` Paul Mackerras
2010-06-07 7:03 ` K.Prasad
2010-06-07 11:25 ` Paul Mackerras
2010-06-09 10:32 ` K.Prasad
2010-06-10 4:23 ` Paul Mackerras [this message]
2010-06-15 1:54 ` Paul Mackerras
2010-06-15 6:09 ` K.Prasad
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=20100610042351.GA17989@drongo \
--to=paulus@samba.org \
--cc=benh@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=prasad@linux.vnet.ibm.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.
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).