From: John Stoffel <john@quad.stoffel.home>
To: Matthew Wilcox <willy@infradead.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>,
Eric Biggers <ebiggers@kernel.org>,
Tyler Hicks <tyhicks@canonical.com>,
linux-fsdevel@vger.kernel.org, ecryptfs@vger.kernel.org,
linux-fscrypt@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] fs: introduce is_dot_dotdot helper for cleanup
Date: Sun, 8 Dec 2019 21:00:41 -0500 [thread overview]
Message-ID: <20191209020041.et776tzhxqsqqfs5@quad.stoffel.home> (raw)
In-Reply-To: <20191208123804.GB32169@bombadil.infradead.org>
On Sun, Dec 08, 2019 at 04:38:04AM -0800, Matthew Wilcox wrote:
> On Sun, Dec 08, 2019 at 03:41:44AM +0000, Al Viro wrote:
> > On Sat, Dec 07, 2019 at 07:35:48PM +0800, Tiezhu Yang wrote:
> > > There exists many similar and duplicate codes to check "." and "..",
> > > so introduce is_dot_dotdot helper to make the code more clean.
> >
> > Umm... No objections, in principle, but... you try to say that name
> > (e.g. in a phone conversation) without stuttering ;-/
> >
> > Any suggestions from native speakers?
>
> I used "is_dot_or_dotdot" when discussing this patch with my wife verbally.
*thumbs up* Both for the wife, and the name. :-)
--
WARNING: multiple messages have this Message-ID (diff)
From: John Stoffel <john@quad.stoffel.home>
To: Matthew Wilcox <willy@infradead.org>
Cc: ecryptfs@vger.kernel.org, "Theodore Y. Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org, Tyler Hicks <tyhicks@canonical.com>,
Eric Biggers <ebiggers@kernel.org>,
linux-fscrypt@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] fs: introduce is_dot_dotdot helper for cleanup
Date: Sun, 8 Dec 2019 21:00:41 -0500 [thread overview]
Message-ID: <20191209020041.et776tzhxqsqqfs5@quad.stoffel.home> (raw)
In-Reply-To: <20191208123804.GB32169@bombadil.infradead.org>
On Sun, Dec 08, 2019 at 04:38:04AM -0800, Matthew Wilcox wrote:
> On Sun, Dec 08, 2019 at 03:41:44AM +0000, Al Viro wrote:
> > On Sat, Dec 07, 2019 at 07:35:48PM +0800, Tiezhu Yang wrote:
> > > There exists many similar and duplicate codes to check "." and "..",
> > > so introduce is_dot_dotdot helper to make the code more clean.
> >
> > Umm... No objections, in principle, but... you try to say that name
> > (e.g. in a phone conversation) without stuttering ;-/
> >
> > Any suggestions from native speakers?
>
> I used "is_dot_or_dotdot" when discussing this patch with my wife verbally.
*thumbs up* Both for the wife, and the name. :-)
--
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: John Stoffel <john@quad.stoffel.home>
To: Matthew Wilcox <willy@infradead.org>
Cc: ecryptfs@vger.kernel.org, "Theodore Y. Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org, Tyler Hicks <tyhicks@canonical.com>,
Eric Biggers <ebiggers@kernel.org>,
linux-fscrypt@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v3] fs: introduce is_dot_dotdot helper for cleanup
Date: Sun, 8 Dec 2019 21:00:41 -0500 [thread overview]
Message-ID: <20191209020041.et776tzhxqsqqfs5@quad.stoffel.home> (raw)
In-Reply-To: <20191208123804.GB32169@bombadil.infradead.org>
On Sun, Dec 08, 2019 at 04:38:04AM -0800, Matthew Wilcox wrote:
> On Sun, Dec 08, 2019 at 03:41:44AM +0000, Al Viro wrote:
> > On Sat, Dec 07, 2019 at 07:35:48PM +0800, Tiezhu Yang wrote:
> > > There exists many similar and duplicate codes to check "." and "..",
> > > so introduce is_dot_dotdot helper to make the code more clean.
> >
> > Umm... No objections, in principle, but... you try to say that name
> > (e.g. in a phone conversation) without stuttering ;-/
> >
> > Any suggestions from native speakers?
>
> I used "is_dot_or_dotdot" when discussing this patch with my wife verbally.
*thumbs up* Both for the wife, and the name. :-)
--
next prev parent reply other threads:[~2019-12-09 2:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 11:35 [PATCH v3] fs: introduce is_dot_dotdot helper for cleanup Tiezhu Yang
2019-12-07 11:35 ` Tiezhu Yang
2019-12-07 11:35 ` [f2fs-dev] " Tiezhu Yang
2019-12-08 3:41 ` Al Viro
2019-12-08 3:41 ` [f2fs-dev] " Al Viro
2019-12-08 12:38 ` Matthew Wilcox
2019-12-08 12:38 ` [f2fs-dev] " Matthew Wilcox
2019-12-09 2:00 ` John Stoffel [this message]
2019-12-09 2:00 ` John Stoffel
2019-12-09 2:00 ` [f2fs-dev] " John Stoffel
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=20191209020041.et776tzhxqsqqfs5@quad.stoffel.home \
--to=john@quad.stoffel.home \
--cc=ebiggers@kernel.org \
--cc=ecryptfs@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tyhicks@canonical.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=yangtiezhu@loongson.cn \
--cc=yuchao0@huawei.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.