From: "David Rivshin (Allworx)" <drivshin.allworx@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: johannes@sipsolutions.net, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: pull-request: mac80211 2015-12-15
Date: Thu, 17 Dec 2015 13:10:27 -0500 [thread overview]
Message-ID: <20151217131027.5af2a0f5.drivshin.allworx@gmail.com> (raw)
In-Reply-To: <20151217.120448.2070217640292112574.davem@davemloft.net>
On Thu, 17 Dec 2015 12:04:48 -0500 (EST)
David Miller <davem@davemloft.net> wrote:
> From: Johannes Berg <johannes@sipsolutions.net>
> Date: Thu, 17 Dec 2015 13:44:32 +0100
>
> > On Wed, 2015-12-16 at 18:34 -0500, David Miller wrote:
> >>
> >> Something about your text encoding kept this from ending up
> >> in patchwork for some reason.
> >>
> >
> > Hm. I don't see anything special with this, seems to just be plain
> > text 8bit transfer encoding.
> >
> > Do you want me to watch out for things getting into patchwork in the
> > future?
>
> Look in the quoted text of mine, see that underline thing after
> the ">>"? Where are those coming from? Those were all over the
> place in your pull request and tripped up patchwork's parser I
> guess.
I was curious and took a look. I suspect what you're seeing are the UTF-8
<0xC2 0xA0> sequence, which translates to codepoint 0x00A0 "no-break space"
(same as in latin1). They seem to have been used in place of regular spaces
for the purpose of indenting. The Content-Type charset in Johannes' emails
is "UTF-8", so I think that's legal. Although I have no idea how Patchwork
reacts to it.
next prev parent reply other threads:[~2015-12-17 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 12:30 pull-request: mac80211 2015-12-15 Johannes Berg
2015-12-16 23:34 ` David Miller
2015-12-17 12:44 ` Johannes Berg
2015-12-17 17:04 ` David Miller
2015-12-17 18:10 ` David Rivshin (Allworx) [this message]
2015-12-17 19:11 ` Joe Perches
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=20151217131027.5af2a0f5.drivshin.allworx@gmail.com \
--to=drivshin.allworx@gmail.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).