From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] vfs.git #work.misc
Date: Sat, 13 Aug 2022 17:39:15 -0700 [thread overview]
Message-ID: <CAHk-=whwCrp6Mok6fccY1uXQQEUCcyPSjNvsHYrnaaL90-85sw@mail.gmail.com> (raw)
In-Reply-To: <YvhAZYm1T4ni+y01@ZenIV>
On Sat, Aug 13, 2022 at 5:23 PM Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> vfs: escape hash as well
That didn't parse at all for me - when talking about hashes in the
kernel, we basically never talk about the hash _character_ ('#'), and
your pull request message just made me go all "Whaa?"
Next time, can we agree to talk about either 'hash character' or just say '#'?
Just to avoid the confusion with all the normal hashing we do in the kernel.
Linus
next prev parent reply other threads:[~2022-08-14 0:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 0:23 [git pull] vfs.git #work.misc Al Viro
2022-08-14 0:39 ` Linus Torvalds [this message]
2022-08-14 0:39 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-03-11 0:39 Al Viro
2019-03-12 22:20 ` pr-tracker-bot
2017-11-17 3:04 [git pull] vfs.git work.misc Al Viro
2016-05-18 18:40 [git pull] vfs.git#work.misc Al Viro
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='CAHk-=whwCrp6Mok6fccY1uXQQEUCcyPSjNvsHYrnaaL90-85sw@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).