From: Linus Torvalds <torvalds@osdl.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Loops in the Signed-off-by process
Date: Fri, 1 Oct 2004 12:39:21 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0410011233370.2403@ppc970.osdl.org> (raw)
In-Reply-To: <1096658717.3684.980.camel@localhost>
On Fri, 1 Oct 2004, Dave Hansen wrote:
>
> Or, does it even really matter?
I don't think it matters that much, although I personally prefer to see
the person who sent it to me ("touched it last") be last in the list.
That's partly because of the fact that especially with bigger merges (ie
with Andrew), I just do a search-and-replace, and replace any "signed off
by sender" with "signed off by sender and me".
At the same time, I think it's pretty unnecessary (and possibly confusing)
to have somebody mentioned twice, so I'd actually prefer to see people
just move their (previous) sign-off to be last when they send it on.
Side note: I also like seeing "Acked-by:" or "Cc:" things just above the
sign-off lines, because it ends up being useful if there are any technical
issues with the patch - if a bug is found, it's very convenient to just
take all the sign-off people _and_ the other "involved" people and send
off a query to them all. Even if that "Acked-by:" has no other meaning
than as a mention of the fact that somebody else was involved in
discussions, even if they may not have been involved in actually writing
or passing off the ptch.
Linus
next prev parent reply other threads:[~2004-10-01 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 19:25 Dave Hansen
2004-10-01 19:39 ` Linus Torvalds [this message]
2004-10-01 20:40 ` Paul Jackson
2004-10-01 20:51 ` Linus Torvalds
2004-10-01 21:11 ` alan
2004-10-01 22:20 ` Linus Torvalds
2004-10-01 21:36 ` alan
2004-10-02 17:29 ` Alan Cox
2004-10-02 17:40 ` alan
2004-10-03 1:04 ` Benjamin Herrenschmidt
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=Pine.LNX.4.58.0410011233370.2403@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.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 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®