Loops in the Signed-off-by process

[Dave Hansen]

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/