Who wrote - and approved - 2.6.22
Posted Jun 15, 2007 16:25 UTC (Fri) by aegl
In reply to: Who wrote - and approved - 2.6.22
Parent article: Who wrote - and approved - 2.6.22
It isn't a sure bet that a change-set with a sign-off from Linus has actually been reviewed by him either ... when Andrew Morton sends a "patch-bomb" with several hundred e-mail messages moving code from -mm to Linus, chances are that Linus does not sit down and read each and every one of them. But they will all get a "Signed-off-by" from Linus because the GIT tool that applies patches from a mailbox adds a sign-off to each commit that is applied that way.
If Andrew started using a GIT tree to transfer to Linus, then many of those "Signed-off-by: Linus" commits would just end the trail-of-blame with Andrew's sign-off.
This is sort of documented in Documentation/SubmittingPatches: "The Signed-off-by: tag indicates that the signer was involved in the
development of the patch, or that he/she was in the patch's delivery path.". "In the patches delivery path" does not necessarily mean "Reviewed by".
So some care is needed when interpreting this data since some quite large parts are affected by the mechanisms used to move changes around.
to post comments)