linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent McIntyre <vincent.mcintyre@gmail.com>
To: Johannes Stezenbach <js@linuxtv.org>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: patchowork parsing issue?
Date: Thu, 5 Dec 2019 20:35:46 +1100	[thread overview]
Message-ID: <CAEsFdVPRpPefJxXQj9qFPU39OTKWcy8jp7=0u3+ekpXETbJa8w@mail.gmail.com> (raw)
In-Reply-To: <20191204121906.GA21908@linuxtv.org>

Thank you Johannes for taking the time to spot the wrapped line.
I did actually find that document...after I sent my email.
I'll resend from a saner mail service.
Regards
Vince


On 12/4/19, Johannes Stezenbach <js@linuxtv.org> wrote:
> On Wed, Dec 04, 2019 at 08:40:59PM +1100, Vincent McIntyre wrote:
>>
>>   https://patchwork.linuxtv.org/patch/60186/
>>   https://patchwork.linuxtv.org/patch/59979/
>>
>> but it doesn't look right when it gets there. For some reason,
>> the last hunk of the patch is included with the patch description.
>> This was why I resent it the first time, I thought I must have
>> messed up the formatting.
>>
>> Admittedly I'm sending from gmail's web interface but I have taken
>> some care to get the text correctly formatted and patchwork did the
>> same thing with it twice, so I'm starting to wonder if there's an issue
>> with patchwork.
> ...
>> @@ -539,7 +546,7 @@ build - Builds the media drivers without needing
>> to compile a new kernel
>
> This line seems to be wrapped.
>
> Quoting
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/email-clients.rst
>
>   Gmail (Web GUI)
>   ***************
>
>   Does not work for sending patches.
>
>   Gmail web client converts tabs to spaces automatically.
>
>   At the same time it wraps lines every 78 chars with CRLF style line
> breaks
>   although tab2space problem can be solved with external editor.
>
>   Another problem is that Gmail will base64-encode any message that has a
>   non-ASCII character. That includes things like European names.
>
>
> HTH,
> Johannes
>

      reply	other threads:[~2019-12-05  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04  9:40 patchowork parsing issue? Vincent McIntyre
2019-12-04 12:19 ` Johannes Stezenbach
2019-12-05  9:35   ` Vincent McIntyre [this message]

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='CAEsFdVPRpPefJxXQj9qFPU39OTKWcy8jp7=0u3+ekpXETbJa8w@mail.gmail.com' \
    --to=vincent.mcintyre@gmail.com \
    --cc=js@linuxtv.org \
    --cc=linux-media@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).