From: "zhangyi (F)" <yi.zhang@huawei.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Theodore Ts'o <tytso@mit.edu>
Cc: 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 09:33:54 +0800 [thread overview]
Message-ID: <ca33cb6a-9be9-1a2c-efa3-1dc5996897f6@huawei.com> (raw)
In-Reply-To: <CAHk-=wjahvxdYmEgZEOqSSOVdTP-Njqbh6e8=PDVtt4Md7qHNg@mail.gmail.com>
On 2021/3/22 6:23, Linus Torvalds wrote:
> On Sun, Mar 21, 2021 at 11:31 AM Theodore Ts'o <tytso@mit.edu> wrote:
>>
>> zhangyi (F) (3):
>> ext4: find old entry again if failed to rename whiteout
>> ext4: do not iput inode under running transaction in ext4_rename()
>> ext4: do not try to set xattr into ea_inode if value is empty
>
> Side note: this is obviously entirely up to the author, but I think it
> would be nice if we would encourage people to use their native names
> if/when they want to.
>
> Maybe this "zhangyi (F)" is how they _want_ to write their name in the
> kernel, and that's obviously fine if so.
>
> But at the same time, coming from Finland, I remember how people who
> had the "odd" characters (åäö) in their name ended up replacing them
> with the US-ASCII version (generally "aa" "ae" and "oe"), and it
> always just looked bad to a native speaker. Particularly annoying in
> public contexts.
>
> At the same time, for the same reason, I can also understand people
> not wanting to even expose those characters at all, because then
> non-native speakers invariably messed it up even worse...
>
> Anyway, I think and hope that we have the infrastructure to do it
> right not just for Latin1, but the more complex non-Western character
> sets too.
>
> And as a result should possibly encourage people to use their native
> names if they want to. At least make people aware that it _should_
> work.
>
> Again, maybe I'm barking up the wrong tree, and in this case "zhangyi
> (F) <yi.zhang@huawei.com>" is just what zhangyi prefers simply because
> it's easier/more convenient.
>
> But I just wanted to mention it, because we _do_ have examples of it
> working. Not many, but some:
>
> git log --pretty="%an" --since=2.years | sort -u | tail
>
> including examples of having the Westernized name in parenthesis for
> the "use that one if you can't do the real one" case..
>
Hi, Linus.
I will use my real name "Yi Zhang" next time.
Thanks,
Yi.
next prev parent reply other threads:[~2021-03-22 1:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 18:31 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) [this message]
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
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=ca33cb6a-9be9-1a2c-efa3-1dc5996897f6@huawei.com \
--to=yi.zhang@huawei.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
all inboxes | Powered by JetHome®