Linux Documentation
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Billy Wilson <billy_wilson@byu.edu>
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: Correct the release date of 5.2 stable
Date: Tue, 11 Aug 2020 10:49:07 -0600	[thread overview]
Message-ID: <20200811104907.719c60c3@lwn.net> (raw)
In-Reply-To: <20200806231754.7735-1-billy_wilson@byu.edu>

On Thu,  6 Aug 2020 17:17:54 -0600
Billy Wilson <billy_wilson@byu.edu> wrote:

> A table lists the 5.2 stable release date as September 15, but it was
> released on July 7. This may confuse a reader who is trying to
> understand the stable update release cycle.
> 
> Signed-off-by: Billy Wilson <billy_wilson@byu.edu>
> ---
>  Documentation/process/2.Process.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/process/2.Process.rst b/Documentation/process/2.Process.rst
> index 3588f48841eb..4ae1e0f600c1 100644
> --- a/Documentation/process/2.Process.rst
> +++ b/Documentation/process/2.Process.rst
> @@ -113,7 +113,7 @@ than one development cycle past their initial release. So, for example, the
>  5.2 kernel's history looked like this (all dates in 2019):
>  
>  	==============  ===============================
> -	September 15 	5.2 stable release
> +	July 7		5.2 stable release
>  	July 14		5.2.1

Applied, thanks.

jon

      parent reply	other threads:[~2020-08-11 16:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 23:17 [PATCH] docs: Correct the release date of 5.2 stable Billy Wilson
2020-08-06 23:46 ` Randy Dunlap
2020-08-07  0:08   ` Billy Wilson
2020-08-07  0:41     ` Randy Dunlap
2020-08-07  3:51       ` Billy Wilson
2020-08-07  5:06         ` Randy Dunlap
2020-08-11 16:49 ` Jonathan Corbet [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=20200811104907.719c60c3@lwn.net \
    --to=corbet@lwn.net \
    --cc=billy_wilson@byu.edu \
    --cc=linux-doc@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