All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Boyang <zhangboyang.id@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-next@vger.kernel.org, song@kernel.org, wei.liu@kernel.org,
	jszhang@kernel.org, chenhuacai@kernel.org, guoren@kernel.org,
	xiang@kernel.org, chao@kernel.org, ming.lei@redhat.com,
	bhe@redhat.com, longman@redhat.com, wqu@suse.com, yhs@fb.com,
	haoluo@google.com, decui@microsoft.com, siyanteng@loongson.cn
Subject: [RESEND] Please consider name next Linux release "I love Linux" (Re: Linux 5.19)
Date: Thu, 11 Aug 2022 22:02:15 +0800	[thread overview]
Message-ID: <61d77412-af1a-5b00-9754-f156b1c63a74@gmail.com> (raw)
In-Reply-To: <CAHk-=wgrz5BBk=rCz7W28Fj_o02s0Xi0OEQ3H1uQgOdFvHgx0w@mail.gmail.com>

Hi,

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 name the next Linux release (5.20 or 6.0) "I 
love linux" ? The number "5.20" is a wordplay in Chinese, which means "I 
love you" [1], thus "Linux 5.20" can be read as "I love Linux" in Chinese.

Even if next kernel version is 6.0, I think it's probably a good idea 
for both Chinese-speakers and non-Chinese speakers to express our love 
to Linux Kernel.

The name of Linux kernel release has a long history of play-on-words 
[2]. For example, 5.15 is named "Trick or Treat" and 5.17 is named 
"Superb Owl".

[1] https://en.wikipedia.org/wiki/Chinese_Internet_slang

[2] https://en.wikipedia.org/wiki/Linux_kernel_version_history

Thanks and regards,
Zhang Boyang

  parent reply	other threads:[~2022-08-11 14:02 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
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 ` Zhang Boyang [this message]
2022-08-12  2:39   ` [RESEND] Please consider name next Linux release "I love Linux" (Re: Linux 5.19) 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=61d77412-af1a-5b00-9754-f156b1c63a74@gmail.com \
    --to=zhangboyang.id@gmail.com \
    --cc=bhe@redhat.com \
    --cc=chao@kernel.org \
    --cc=chenhuacai@kernel.org \
    --cc=decui@microsoft.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=guoren@kernel.org \
    --cc=haoluo@google.com \
    --cc=jszhang@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=ming.lei@redhat.com \
    --cc=siyanteng@loongson.cn \
    --cc=song@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wei.liu@kernel.org \
    --cc=wqu@suse.com \
    --cc=xiang@kernel.org \
    --cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.