On 22.11.21 21:24, Steven Rostedt wrote: > On Mon, 22 Nov 2021 19:50:35 +0100 > Thorsten Leemhuis <linux@xxxxxxxxxxxxx> wrote: > >>> That said, I would like a way to have versions show a link to the last >>> version that was reviewed. >>> >>> v1: has no tags >>> >>> v2: has a Reviewed: tag to v1. >>> >>> v3: has a Reviewed: tag to v2 >>> >>> [...] >>> >>> Then the final commit could have a "Link" or "Reviewed" tag to v3, even >>> though there may not be any reviews to v3, but v3 has the link to v2, and >>> v2 has the link to v1, etc. >> >> Is that really worth it? Isn't it sufficient if the commit links to the >> last public review posting, as that already should link to all earlier >> review postings. Sure, not everybody is doing this right now, but maybe >> just educating people to do so is better than creating something new. > > Isn't "as that already should link to all earlier review postings" what I'm > suggesting above? I haven't seen many people do that yet. Yeah, you are right, sorry, my perception was wrong. Any maybe I got your suggestion wrong, but what you suggested sounded to me like "each patch should link to the previous submission of the patch". I just wonder if it's way easier and sufficient if just the cover letter links to the previous or all earlier submissions of the series in its revision history (sorry, I didn't should have made this more obvious in my earlier mail); for patches without a cover letter this obligation obviously would shift to the patch. IOW: I have something in mind like in this submission: https://lore.kernel.org/lkml/cover.1637252610.git.sander@xxxxxxxxxxxxx/ Only the cover letter links to the earlier version, not the individual patches. But I have no strong feeling here, I don't care much about this. Ciao, Thorsten
