public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB•COM>
To: 'Zhang Boyang' <zhangboyang.id@gmail•com>,
	Linus Torvalds <torvalds@linux-foundation•org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Cc: "loongarch@lists•linux.dev" <loongarch@lists•linux.dev>,
	"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>
Subject: RE: Please consider Linux 5.20 because it means "I love Linux" in Chinese (Re: Linux 5.19)
Date: Sun, 7 Aug 2022 17:21:38 +0000	[thread overview]
Message-ID: <7ba6f61ee9494fcc92268de4d32bf89e@AcuMS.aculab.com> (raw)
In-Reply-To: <9bc1f1f4-3923-be9e-ee13-9c8252a56643@gmail.com>

From: Zhang Boyang
> Sent: 05 August 2022 18:00
> 
> On 2022/8/1 05:43, Linus Torvalds wrote:
> > (*) I'll likely call it 6.0 since I'm starting to worry about getting
> > confused by big numbers again.
> 
> Could you please consider use 5.20 as next version number instead of
> 6.0? "5.20" is a wordplay number in Chinese, which means "I love you".
> Thus "Linux 5.20" can be read as "I love Linux" in Chinese. So I think
> it's good thing to release something like "Linux 5.20 I love linux
> edition", just like "Linux For Workgroups 3.11" in the past.

I was thinking he should do 5.20, 5.21 and 5.22 before 6.0.
Just to stop anyone thinking it always changed after .19.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  reply	other threads:[~2022-08-07 17:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHk-=wgrz5BBk=rCz7W28Fj_o02s0Xi0OEQ3H1uQgOdFvHgx0w@mail.gmail.com>
2022-08-05 17:00 ` Please consider Linux 5.20 because it means "I love Linux" in Chinese (Re: Linux 5.19) Zhang Boyang
2022-08-07 17:21   ` David Laight [this message]
2022-08-11 14:02 ` [RESEND] Please consider name next Linux release "I love Linux" " Zhang Boyang
2022-08-12  2:39   ` Baoquan He
2022-08-12  3:28     ` Huacai Chen
2022-08-12  6:31       ` Gao Xiang
2022-08-12  8:22         ` YanTeng Si
2022-08-13 17:17     ` Zhang Boyang
2022-08-14 15:22     ` WANG Xuerui

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=7ba6f61ee9494fcc92268de4d32bf89e@AcuMS.aculab.com \
    --to=david.laight@aculab$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=loongarch@lists$(echo .)linux.dev \
    --cc=torvalds@linux-foundation$(echo .)org \
    --cc=zhangboyang.id@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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