From: NeilBrown <neilb@suse.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Ian Kent <raven@themaw.net>,
autofs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH/RFC] autofs: the documentation I wanted to read
Date: Thu, 31 Jul 2014 14:06:27 +1000 [thread overview]
Message-ID: <20140731140627.5c5bfb06@notabene.brown> (raw)
In-Reply-To: <53D93B5A.1040707@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
On Wed, 30 Jul 2014 11:37:14 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
> On 07/28/14 19:00, NeilBrown wrote:
> > +Directories further down the tree depend on the *max_proto* mount
>
> max_proto or maxproto? or either?
> check/fix other places also.
The mount option is "maxproto", the internal variable name is
"max_proto" :-)
>
> Thanks. Nice job.
>
Thanks so much for all those improvements - I really appreciate it.
They'll all be in the next posting.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-07-31 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 2:00 NeilBrown
2014-07-30 18:37 ` Randy Dunlap
2014-07-31 4:06 ` NeilBrown [this message]
2014-08-01 5:47 ` Ian Kent
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=20140731140627.5c5bfb06@notabene.brown \
--to=neilb@suse.de \
--cc=autofs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=rdunlap@infradead.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
Powered by JetHome