From: Dave Hansen <haveblue@us.ibm.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@osdl.org>
Subject: Loops in the Signed-off-by process
Date: Fri, 01 Oct 2004 12:25:17 -0700 [thread overview]
Message-ID: <1096658717.3684.980.camel@localhost> (raw)
With the recent ppc64 updates, a few patches in my tree didn't merge
very easily. Being lazy, I asked one of the ppc64 developers to resync
them for me. But, it happened to be someone other than the original
author that did this.
When they got sent to me again, the original author's (and my)
Signed-off-by: lines were gone, replaced by the nice fellow who merged
them. This was certainly an artifact of how he generates patches and
obviously not malicious, but I still wonder what the "right" thing to do
is.
Do we show the logical flow?
Signed-off-by: original author
Signed-off-by: patch merger
Signed-off-by: tree maintainer
Or the actual flow of the patches, showing that they came back to the
tree maintainer twice?
Signed-off-by: original author
Signed-off-by: tree maintainer
Signed-off-by: patch merger
Signed-off-by: tree maintainer
Or, does it even really matter?
-- Dave
next reply other threads:[~2004-10-01 19:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 19:25 Dave Hansen [this message]
2004-10-01 19:39 ` Loops in the Signed-off-by process Linus Torvalds
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=1096658717.3684.980.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox