From: Al Viro <viro@ZenIV.linux.org.uk>
To: Sean Anderson <seanga2@gmail.com>
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: Thu, 7 Jun 2018 19:31:43 +0100 [thread overview]
Message-ID: <20180607183143.GT30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <86caf9d3-a520-bb4c-b174-954966c844e4@gmail.com>
On Tue, Jun 05, 2018 at 03:46:37PM -0400, Sean Anderson wrote:
> -----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.
Useful test: if git am barfs on your mail (which it does for the
first posting in the thread), you are going to annoy people...
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Sean Anderson <seanga2@gmail.com>
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: Thu, 7 Jun 2018 19:31:43 +0100 [thread overview]
Message-ID: <20180607183143.GT30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <86caf9d3-a520-bb4c-b174-954966c844e4@gmail.com>
On Tue, Jun 05, 2018 at 03:46:37PM -0400, Sean Anderson wrote:
> -----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.
Useful test: if git am barfs on your mail (which it does for the
first posting in the thread), you are going to annoy people...
next prev parent reply other threads:[~2018-06-07 18:31 UTC|newest]
Thread overview: 7+ 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-05-26 3:41 ` Al Viro
2018-06-05 19:46 ` Sean Anderson
2018-06-05 19:46 ` Sean Anderson
2018-06-07 18:31 ` Al Viro [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=20180607183143.GT30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=corbet@lwn.net \
--cc=jlayton@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=seanga2@gmail.com \
--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 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.