public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Loops in the Signed-off-by process
@ 2004-10-01 19:25 Dave Hansen
  2004-10-01 19:39 ` Linus Torvalds
  0 siblings, 1 reply; 10+ messages in thread
From: Dave Hansen @ 2004-10-01 19:25 UTC (permalink / raw)
  To: Linux Kernel Mailing List; +Cc: Linus Torvalds

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


^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2004-10-03  1:10 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-01 19:25 Loops in the Signed-off-by process Dave Hansen
2004-10-01 19:39 ` 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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox