From: Daniel Walker <dwalker@fifo99.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Kay, Allen M" <allen.m.kay@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH] enabling ACS P2P upstream forwarding
Date: Wed, 16 Sep 2009 09:39:13 -0700 [thread overview]
Message-ID: <1253119153.11643.583.camel@desktop> (raw)
In-Reply-To: <20090916093446.5ea81b8a@bike.lwn.net>
On Wed, 2009-09-16 at 09:34 -0600, Jonathan Corbet wrote:
> On Tue, 15 Sep 2009 17:12:17 -0700
> Daniel Walker <dwalker@fifo99.com> wrote:
>
> > Both times that you've submitted this the patch has been corrupt.. Your
> > mailer, or something is adding little "=20" or "=3D" all over.
>
> That looks a lot like *your* mail client not understanding
> quoted-printable encoding. QP can be a pain, but it is a legitimate
> encoding; the message in question looks fine in claws.
Shouldn't all patches be sent as plain text untouched? I don't think I
should necessarily need a specific email client to strip off some
characters..
Daniel
next prev parent reply other threads:[~2009-09-16 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 23:44 [PATCH] enabling ACS P2P upstream forwarding Kay, Allen M
2009-09-16 0:12 ` Daniel Walker
2009-09-16 0:13 ` Kay, Allen M
2009-09-16 0:24 ` Daniel Walker
2009-09-16 5:46 ` Grant Grundler
2009-09-16 9:05 ` Daniel Walker
2009-09-16 15:34 ` Jonathan Corbet
2009-09-16 16:39 ` Daniel Walker [this message]
2009-09-16 16:41 ` Alan Cox
2009-09-16 16:58 ` Daniel Walker
2009-09-16 9:57 ` Matthew Wilcox
2009-09-17 2:14 ` Kay, Allen M
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=1253119153.11643.583.camel@desktop \
--to=dwalker@fifo99.com \
--cc=allen.m.kay@intel.com \
--cc=corbet@lwn.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 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.