Linux Documentation
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/1] docs: submitting-patches: Emphasise the requirement to Cc: stable when using Fixes: tag
Date: Wed, 13 Jan 2021 17:22:13 +0100	[thread overview]
Message-ID: <X/8eNVSQo5SY2mQn@kroah.com> (raw)
In-Reply-To: <20210113160859.GE3975472@dell>

On Wed, Jan 13, 2021 at 04:08:59PM +0000, Lee Jones wrote:
> On Wed, 13 Jan 2021, Greg Kroah-Hartman wrote:
> 
> > On Wed, Jan 13, 2021 at 02:23:47PM +0000, Lee Jones wrote:
> > > Clear-up any confusion surrounding the Fixes: tag with regards to the
> > > need to Cc: the stable mailing list when submitting stable patch
> > > candidates.
> > > 
> > > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Cc: Jonathan Corbet <corbet@lwn.net>
> > > Cc: linux-doc@vger.kernel.org
> > > Signed-off-by: Lee Jones <lee.jones@linaro.org>
> > > ---
> > >  Documentation/process/submitting-patches.rst | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> > > index 7c97ad580e7d0..636ef067c1565 100644
> > > --- a/Documentation/process/submitting-patches.rst
> > > +++ b/Documentation/process/submitting-patches.rst
> > > @@ -554,7 +554,8 @@ is used to make it easy to determine where a bug originated, which can help
> > >  review a bug fix. This tag also assists the stable kernel team in determining
> > >  which stable kernel versions should receive your fix. This is the preferred
> > >  method for indicating a bug fixed by the patch. See :ref:`describe_changes`
> > > -for more details.
> > > +for more details. Attaching a Fixes: tag does not replace the requirement to
> > > +Cc: stable@vger.kernel.org on all stable patch candidates.
> > 
> > Want to just link to the "stable kernel rules" document here to show
> > the proper way to do this is documented there?
> 
> I think this needs to be clearly stated here.
> 
> What if we linked to the rules document *as well*?

Sure, that works for me.

thanks,

greg k-h

      reply	other threads:[~2021-01-13 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13 14:23 [PATCH 1/1] docs: submitting-patches: Emphasise the requirement to Cc: stable when using Fixes: tag Lee Jones
2021-01-13 15:52 ` Greg Kroah-Hartman
2021-01-13 16:08   ` Lee Jones
2021-01-13 16:22     ` Greg Kroah-Hartman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=X/8eNVSQo5SY2mQn@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=lee.jones@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox