[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211122112916.498810bb@gandalf.local.home>
Date: Mon, 22 Nov 2021 11:29:16 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Thorsten Leemhuis <linux@...mhuis.info>
Cc: workflows@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
Jonathan Corbet <corbet@....net>
Subject: Re: [RFC PATCH v1 1/1] docs: add the new commit-msg tags
'Reported:' and 'Reviewed:'
On Mon, 22 Nov 2021 08:33:42 +0100
Thorsten Leemhuis <linux@...mhuis.info> wrote:
> Introduce the tags 'Reported:' and 'Reviewed:' in addition to 'Link:',
> as the latter is overloaded and hence doesn't indicate what the provided
> URL is about. Documenting these also provides clarity, as a few
> developers have used 'References:' to point to problem reports;
> nevertheless 'Reported:' was chosen for this purpose, as it perfectly
> matches up with the 'Reported-by:' tag commonly used already and needed
> in this situation already.
I like the differences between "Reorted:" and "Reviewed:", although I may
keep the "Link" instead of Reviewed because my automate scripts just give
the link of the patch, and there's seldom a review attached to it :-/
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.
-- Steve
Powered by blists - more mailing lists