[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YvJjKHCo6rod8Yl9@elende.valinor.li>
Date: Tue, 9 Aug 2022 15:37:44 +0200
From: Salvatore Bonaccorso <carnil@...ian.org>
To: Jonathan Corbet <corbet@....net>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Sasha Levin <sashal@...nel.org>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: stable: Document alternative for
referring upstream commit hash
Hi Jonathan,
On Tue, Aug 09, 2022 at 06:54:59AM -0600, Jonathan Corbet wrote:
> Salvatore Bonaccorso <carnil@...ian.org> writes:
>
> > Additionally to the "commit <sha1> upstream." variant, "[ Upstream
> > commit <sha1> ]" is used as well as alternative to refer to the upstream
> > commit hash.
> >
> > Signed-off-by: Salvatore Bonaccorso <carnil@...ian.org>
> > ---
> > Documentation/process/stable-kernel-rules.rst | 6 ++++++
> > 1 file changed, 6 insertions(+)
>
> So this is a nit but...
>
> > diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
> > index c61865e91f52..2fd8aa593a28 100644
> > --- a/Documentation/process/stable-kernel-rules.rst
> > +++ b/Documentation/process/stable-kernel-rules.rst
> > @@ -97,6 +97,12 @@ text, like this:
> >
> > commit <sha1> upstream.
> >
> > +or alternatively:
> > +
> > +.. code-block:: none
> > +
> > + [ Upstream commit <sha1> ]
>
> Can this just be:
>
> or alternatively::
>
> [ Upstream commit <sha1> ]
>
> That extra RST markup just clutters things without any advantage.
Okay, I just have sent a v2 dropping it.
Salvatore
Powered by blists - more mailing lists