From: Sean Anderson <seanga2@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>,
Jeff Layton <jlayton@redhat.com>
Subject: Re: [PATCH RESEND] Documentation: filesystems: update filesystem locking documentation
Date: Tue, 5 Jun 2018 15:46:37 -0400 [thread overview]
Message-ID: <86caf9d3-a520-bb4c-b174-954966c844e4@gmail.com> (raw)
In-Reply-To: <20180526034116.GO30522@ZenIV.linux.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
> Your mission, should you choose to accept it, shall be to locate
> the old sig regarding the usual reaction to use of
> Quoted-Printable...
>
> IOW, fix your mail setup. Applied, but.
Not sure what you mean by "Quoted-Printable"... Is PGP/MIME the
incorrect way to send messages? I've switched to the "traditional"
option for this one, and I've enabled "mail.strictly_mime" in my
settings. Let me know if this fixes things for you.
-----BEGIN PGP SIGNATURE-----
iQGTBAEBCgB9FiEEkGEdW86NSNID6GAoPuiP7LShEG4FAlsW6JxfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkw
NjExRDVCQ0U4RDQ4RDIwM0U4NjAyODNFRTg4RkVDQjRBMTEwNkUACgkQPuiP7LSh
EG6W6wf+MS92RRCzMWTlvdUQZhIdMMzLBwlU3D4Y6eiEWzRz1o7IJxmW+0hmUCws
xo2uC1iUifRSrulYMHOmB5kCRIjL5grpadiJRlJzO1/EKkV4MUA4LlVqh9Z2sXae
o8bxC42/NF+7XKrABBuB+xzi51XGYXG4TevoB/FIMzQIHtnQ0EOkQomAxClm31gx
HbV/GKraYYseINuQ3m1hOdKD+Ior4laySpqbPZLx+8wumIzArlcsXJiw3BpF194W
Blmt5mDNybRPNObEk6huRXsbxoFq95Cu1w8UzFCp2fI6XOZlS9Z+ZrpKixpzFJ2p
lkEPDgrxEeWIA2nxuIsFGwzPnibrpA==
=4mdc
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-06-05 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 2:29 [PATCH RESEND] Documentation: filesystems: update filesystem locking documentation Sean Anderson
2018-05-26 3:41 ` Al Viro
2018-06-05 19:46 ` Sean Anderson [this message]
2018-06-07 18:31 ` Al Viro
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=86caf9d3-a520-bb4c-b174-954966c844e4@gmail.com \
--to=seanga2@gmail.com \
--cc=corbet@lwn.net \
--cc=jlayton@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=willy@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;
as well as URLs for NNTP newsgroup(s).