From: David Disseldorp <ddiss@suse.de>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] exfat: allow access to paths with trailing dots
Date: Wed, 18 Aug 2021 18:40:16 +0200 [thread overview]
Message-ID: <20210818184016.2631aeae@suse.de> (raw)
In-Reply-To: <20210818124835.pdlq25wf7wdn2x57@wittgenstein>
On Wed, 18 Aug 2021 14:48:35 +0200, Christian Brauner wrote:
> On Wed, Aug 18, 2021 at 01:11:21PM +0200, David Disseldorp wrote:
> > This patchset adds a new exfat "keeptail" mount option, which allows
> > users to resolve paths carrying trailing period '.' characters.
> > I'm not a huge fan of "keeptail" as an option name, but couldn't think
> > of anything better.
>
> I wouldn't use "period". The vfs uses "dot" and "dotdot" as seen in e.g.
> LAST_DOT or LAST_DOTOT. Maybe "keep_last_dot"?
Works for me, although I was under the impression that underscores were
avoided for mount options. Also, I think it'd be clearer as the plural
"keep_last_dots".
Cheers, David
next prev parent reply other threads:[~2021-08-18 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 11:11 [PATCH 0/2] exfat: allow access to paths with trailing dots David Disseldorp
2021-08-18 11:11 ` [PATCH 1/2] exfat: add keeptail mount option David Disseldorp
2021-08-18 11:11 ` [PATCH 2/2] exfat: keep trailing dots in paths if keeptail is set David Disseldorp
2021-08-18 12:48 ` [PATCH 0/2] exfat: allow access to paths with trailing dots Christian Brauner
2021-08-18 16:40 ` David Disseldorp [this message]
2021-08-18 17:49 ` Christian Brauner
[not found] <CGME20210820131220epcas1p1e97adf5dfc5125571733d42d5d71110c@epcas1p1.samsung.com>
[not found] ` <20210820151214.37742aad@suse.de>
2021-08-23 4:48 ` Namjae Jeon
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=20210818184016.2631aeae@suse.de \
--to=ddiss@suse.de \
--cc=christian.brauner@ubuntu.com \
--cc=linux-fsdevel@vger.kernel.org \
/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).