From: Steve Dickson <SteveD@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
Linux NFSv4 mailing list <nfsv4@linux-nfs.org>
Subject: Re: [Patch 3/8] NFS Mount Configuration File (Vers 2)
Date: Mon, 03 Aug 2009 11:48:56 -0400 [thread overview]
Message-ID: <4A7706E8.7060106@RedHat.com> (raw)
In-Reply-To: <20090803152409.GB28838@fieldses.org>
On 08/03/2009 11:24 AM, J. Bruce Fields wrote:
> On Mon, Aug 03, 2009 at 10:53:29AM -0400, Steve Dickson wrote:
>> commit 528e270be6bb3e4a072cbbb7f3a8b378b64b7fba
>> Author: Steve Dickson <steved@redhat.com>
>> Date: Mon Mar 9 13:57:10 2009 -0400
>>
>> Store values in lower case. This makes it easier to do string
>> comparisons when reading lists from the configuration file.
>
> Just curious--which parts of the configuration file (section headers,
> keys, values--looks like maybe all 3?) are you making case-insensitive,
> and why do they need to be?
Yes all three of them...
>
> E.g. the idmapd configuration file contains paths and user/group names,
> and both those still need to be case sensitive.
hmm... good point... I would suspect this might be the case for
all users of these routines since pathnames and user/group names
are always case-sensitive....
I would guess both the section and keys can be case-insensitive
but the key probably say case-sensitive...
steved.
next prev parent reply other threads:[~2009-08-03 15:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 14:49 [Patch 0/8] NFS Mount Configuration File (Vers 2) Steve Dickson
2009-08-03 14:51 ` [Patch 1/8] " Steve Dickson
2009-08-03 14:52 ` [Patch 2/8] " Steve Dickson
2009-08-03 14:53 ` [Patch 3/8] " Steve Dickson
2009-08-03 15:24 ` J. Bruce Fields
2009-08-03 15:48 ` Steve Dickson [this message]
2009-08-03 15:56 ` J. Bruce Fields
2009-08-03 16:05 ` Steve Dickson
2009-08-05 19:14 ` Steve Dickson
2009-08-05 19:29 ` J. Bruce Fields
2009-08-05 19:33 ` J. Bruce Fields
2009-08-05 20:03 ` Steve Dickson
2009-08-05 20:02 ` Steve Dickson
2009-08-03 14:54 ` [Patch 4/8] " Steve Dickson
2009-08-03 14:56 ` [Patch 5/8] " Steve Dickson
2009-08-03 14:57 ` [Patch 6/8] " Steve Dickson
2009-08-03 14:59 ` [Patch 7/8] " Steve Dickson
[not found] ` <4A76FB3B.1070004-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-08-03 15:31 ` J. Bruce Fields
2009-08-03 15:53 ` Steve Dickson
[not found] ` <4A7707EA.104-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-08-03 15:57 ` J. Bruce Fields
2009-08-03 15:00 ` [Patch 8/8] " Steve Dickson
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=4A7706E8.7060106@RedHat.com \
--to=steved@redhat.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.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 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.