Linux-Media Archive on lore.kernel.org
 help / color / Atom feed
From: Johannes Stezenbach <js@linuxtv.org>
To: Vincent McIntyre <vincent.mcintyre@gmail.com>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: patchowork parsing issue?
Date: Wed, 4 Dec 2019 13:19:06 +0100
Message-ID: <20191204121906.GA21908@linuxtv.org> (raw)
In-Reply-To: <CAEsFdVOUq4gyue+EZjbE_J_D=W=XnsJBTYGwfk9rV50DJmY+3Q@mail.gmail.com>

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 index

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

Reply instructions:

You may reply publically 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=20191204121906.GA21908@linuxtv.org \
    --to=js@linuxtv.org \
    --cc=linux-media@vger.kernel.org \
    --cc=vincent.mcintyre@gmail.com \
    /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

Linux-Media Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-media/0 linux-media/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-media linux-media/ https://lore.kernel.org/linux-media \
		linux-media@vger.kernel.org
	public-inbox-index linux-media

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-media


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git