Hi all, We've been wanting to gather metrics on Git's code review process - how long it takes from first contact on list to merge, how many iterations are needed, time between iterations, etc. One missing link is the actual merge time in `next` and `master` - a human can infer the link between the patch and the mailing list thread, but it's more challenging for a script to do it. Would it be possible to modify the maintainer workflow to include a link to the cover letter as merged in the merge commit message (or the link to the latest iteration of the patch if it's a single-patch change)? What issues could come up with that workflow? I guess one is that we could move from lore.kernel.org to something else, like we saw the migration from public-inbox.org some years ago. But the Message-ID was preserved between the two archives, so maybe it's enough to include the Message-ID in the merge commit? Another is, of course, the added burden on the maintainer. But maybe there is some script that is already used that we can modify to make the extra load negligible? (Or, even better, if anybody else is already successfully measuring these kinds of metrics without such a reference, could you let me know how you're doing it? :) ) Thanks, - Emily
