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)
next prev parent reply other threads:[~2022-08-07 17:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 21:43 Linux 5.19 Linus Torvalds
2022-08-01 12:47 ` Build regressions/improvements in v5.19 Geert Uytterhoeven
2022-08-02 9:14 ` Geert Uytterhoeven
2022-08-01 16:52 ` Linux 5.19 Tony Luck
2022-08-01 16:59 ` Linus Torvalds
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-09 6:03 ` ext2/zram issue [was: Linux 5.19] Jiri Slaby
2022-08-09 7:59 ` Jiri Slaby
2022-08-09 8:12 ` Jiri Slaby
2022-08-09 8:43 ` Sergey Senozhatsky
2022-08-09 9:11 ` Sergey Senozhatsky
2022-08-09 9:20 ` Sergey Senozhatsky
2022-08-09 10:20 ` Dmitry Rokosov
2022-08-09 11:53 ` Sergey Senozhatsky
2022-08-09 13:15 ` Aleksey Romanov
2022-08-09 13:29 ` Sergey Senozhatsky
2022-08-10 7:06 ` [PATCH] Revert "zram: remove double compression logic" Jiri Slaby
2022-08-10 7:14 ` Sergey Senozhatsky
2022-08-09 12:35 ` ext2/zram issue [was: Linux 5.19] Jiri Slaby
2022-08-09 12:45 ` Jiri Slaby
2022-08-09 12:57 ` Sergey Senozhatsky
2022-08-09 13:07 ` Sergey Senozhatsky
2022-08-09 9:12 ` Lukas Czerner
2022-08-09 9:15 ` Sergey Senozhatsky
2022-08-09 9:53 ` Lukas Czerner
[not found] ` <20220830214626.26544-1-charlie39@cock.li>
2022-08-31 7:55 ` Jiri Slaby
2022-08-11 14:02 ` [RESEND] Please consider name next Linux release "I love Linux" (Re: Linux 5.19) 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.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=zhangboyang.id@gmail.com \
/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
all inboxes | Powered by JetHome®