[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1534527210-1947-1-git-send-email-akinobu.mita@gmail.com>
Date: Sat, 18 Aug 2018 02:33:30 +0900
From: Akinobu Mita <akinobu.mita@...il.com>
To: linux-kernel@...r.kernel.org
Cc: Akinobu Mita <akinobu.mita@...il.com>,
Tim Bird <tim.bird@...y.com>, Jonathan Corbet <corbet@....net>
Subject: [PATCH] docs: fix typo in table describing 4.16 development cycle
Fix s/4.17/4.16/ typo.
Fixes: 8962e40c1993 ("docs: update kernel versions and dates in tables")
Cc: Tim Bird <tim.bird@...y.com>
Cc: Jonathan Corbet <corbet@....net>
Signed-off-by: Akinobu Mita <akinobu.mita@...il.com>
---
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 51d0349..ae020d8 100644
--- a/Documentation/process/2.Process.rst
+++ b/Documentation/process/2.Process.rst
@@ -82,7 +82,7 @@ As an example, here is how the 4.16 development cycle went (all dates in
March 11 4.16-rc5
March 18 4.16-rc6
March 25 4.16-rc7
- April 1 4.17 stable release
+ April 1 4.16 stable release
============== ===============================
How do the developers decide when to close the development cycle and create
--
2.7.4
Powered by blists - more mailing lists