From: Zhang Yi <yi.zhang@huawei.com>
To: Theodore Ts'o <tytso@mit.edu>, Gao Xiang <hsiangkao@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] ext4 fixes for v5.12
Date: Mon, 22 Mar 2021 15:00:33 +0800 [thread overview]
Message-ID: <4d997845-fcc7-93bd-a053-462a12ca7e34@huawei.com> (raw)
In-Reply-To: <YFgQqjkSmCmvZ7LK@mit.edu>
On 2021/3/22 11:36, Theodore Ts'o wrote:
> On Mon, Mar 22, 2021 at 11:05:13AM +0800, Gao Xiang wrote:
>> I think the legel name would be "Zhang Yi" (family name goes first [1])
>> according to
>> The Chinese phonetic alphabet spelling rules for Chinese names [2].
>>
>> Indeed, that is also what the legel name is written in alphabet on our
>> passport or credit/debit cards.
>>
>> Also, many official English-written materials use it in that way, for
>> example, a somewhat famous bastetball player Yao Ming [3][4][5].
>>
>> That is what I wrote my own name as this but I also noticed the western
>> ordering of names is quite common for Chinese people in Linux kernel.
>> Anyway, it's just my preliminary personal thought (might be just my
>> own perference) according to (I think, maybe) formal occasions.
>
> Yeah, there doesn't seem to be a lot of consistency with the ordering
> of Chinese names when they are written in Roman characters. Some
> people put the family name first, and other people will put the
> personal (first) name first. In some cases it may be because the
> developer in question is living in America, and so they've decided to
> use the American naming convention. (Two example of this are former
> ext4 developers Mingming Cao and Jiaying Zhang, who live in Portland
> and Los Angelos, and their family names are Cao and Zhang,
> respectively.)
>
> My personal opinion is people should use whatever name they are
> comfortable with, using whatever characters they prefer. The one
> thing that would be helpful for me is for people to give a hint about
> how they would prefer to be called --- for example, would you prefer
> that start an e-mail with the salutation, "Hi Gao", "Hi Xiang", or "Hi
> Gao Xiang"?
>
> And if I don't know, and I guess wrong, please feel free to correct
> me, either privately, or publically on the e-mail list, if you think
> it would be helpful for more people to understand how you'd prefer to
> be called.
>
Hi, Ted and Xiang
I didn't think about it in depth before, and thanks for your suggestion,
I think use "Zhang Yi" is more suitable for me now.
Thanks,
Yi
next prev parent reply other threads:[~2021-03-22 7:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 18:31 [GIT PULL] ext4 fixes for v5.12 Theodore Ts'o
2021-03-21 21:59 ` pr-tracker-bot
2021-03-21 22:23 ` Linus Torvalds
2021-03-22 1:33 ` zhangyi (F)
2021-03-22 3:00 ` Theodore Ts'o
2021-03-22 12:10 ` Herbert Xu
2021-03-22 15:12 ` Theodore Ts'o
2021-03-22 3:05 ` Gao Xiang
2021-03-22 3:36 ` Theodore Ts'o
2021-03-22 3:47 ` Gao Xiang
2021-03-22 7:00 ` Zhang Yi [this message]
2021-03-22 8:55 ` Oleksandr Natalenko
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=4d997845-fcc7-93bd-a053-462a12ca7e34@huawei.com \
--to=yi.zhang@huawei.com \
--cc=hsiangkao@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).