From: Trond Myklebust <trondmy@primarydata.com>
To: "SteveD@redhat.com" <SteveD@redhat.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: /etc/exports parsing is borked again in nfs-utils
Date: Sat, 25 Jun 2016 20:12:03 +0000 [thread overview]
Message-ID: <1466885520.9316.4.camel@primarydata.com> (raw)
W3Jvb3RAbGVpcmEgbmZzXSMgY2F0IC9ldGMvZXhwb3J0cw0KL2V4cG9ydAkJLXJvLHNlYz1zeXMs
c3luYwlsb2NhbGhvc3Qocncsbm9fcm9vdF9zcXUNCmFzaCkNCltyb290QGxlaXJhIG5mc10jIGV4
cG9ydGZzIC1ydg0KZXhwb3J0aW5nIGxvY2FsaG9zdDovZXhwb3J0DQpbcm9vdEBsZWlyYSBuZnNd
IyBtb3VudCAtdCBuZnMgbG9jYWxob3N0Oi9leHBvcnQgL21udC9uZnMNCltyb290QGxlaXJhIG5m
c10jIG1rZGlyIC9tbnQvbmZzL2dudXJyDQpta2RpcjogY2Fubm90IGNyZWF0ZSBkaXJlY3Rvcnkg
4oCYL21udC9uZnMvZ251cnLigJk6IFJlYWQtb25seSBmaWxlIHN5c3RlbQ0KDQoNCk5vdGUgdGhh
dCByZW1vdmluZyB0aGUgInNlYz1zeXMiIGFib3ZlIGNhdXNlcyB0aGUgdGVzdCB0byBzdWNjZWVk
Lg0KDQotLSANCg0KVHJvbmQgTXlrbGVidXN0DQpMaW51eCBORlMgY2xpZW50IG1haW50YWluZXIs
IFByaW1hcnlEYXRhDQp0cm9uZC5teWtsZWJ1c3RAcHJpbWFyeWRhdGEuY29tDQo=
next reply other threads:[~2016-06-25 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-25 20:12 Trond Myklebust [this message]
2016-06-30 15:42 ` /etc/exports parsing is borked again in nfs-utils Steve Dickson
2016-06-30 15:59 ` Trond Myklebust
2016-07-05 18:45 ` Steve Dickson
2016-07-05 19:06 ` 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=1466885520.9316.4.camel@primarydata.com \
--to=trondmy@primarydata.com \
--cc=SteveD@redhat.com \
--cc=linux-nfs@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).