qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: jan.kiszka@web.de
Subject: Re: [Qemu-devel] Re: [PATCH, RFC] Add file describing rules for submitting patches
Date: Mon, 20 Apr 2009 09:23:46 -0500	[thread overview]
Message-ID: <49EC8572.9080606@codemonkey.ws> (raw)
In-Reply-To: <20090419.114116.371475325.imp@bsdimp.com>

M. Warner Losh wrote:
> In message: <49EB55D8.7020903@web.de>
>             Jan Kiszka <jan.kiszka@web.de> writes:
> : Blue Swirl wrote:
> : > Hi,
> : > 
> : > I gathered a few common complaints about patch submission, hopefully
> : > not too much affected by my consumption of small amounts of various
> : > alcoholic substances.
> : 
> : Don't drink and patch. Oh, wait, this was: "Don't drink and derive!" So
> : this is probably ok.
> : 
> : > 
> : > Comments, objections?
> : 
> : SP3.2: If you only attach, pleeeease don't use base64 encoding etc. And
> : there should be no maintainer exception...
>
> How can you attach a patch with MIME and not do that?
>   

If you tolerate MIME, you have to accept different encoding types 
(including base64).  Right now, just accepting text/plain and 
text/x-diff seems to work well enough.  The most common failure for my 
scripts wrt attachments is with mailers that do application/binary or 
some similarly opaque mime type.  What's particularly bad are mailers 
that send a plain text descriptions, HTML descriptions, and then the 
patch.  This last two categories are too difficult to handle correctly 
in scripts so that's where I want to bounce.  It's not a huge problem 
though.  It only happens in < %1 of patches.

Regards,

Anthony Liguori

> Warner
>
>
>   

  parent reply	other threads:[~2009-04-20 14:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 15:32 [Qemu-devel] [PATCH, RFC] Add file describing rules for submitting patches Blue Swirl
2009-04-19 16:11 ` Avi Kivity
2009-04-19 16:59   ` Blue Swirl
2009-04-19 17:36     ` Andreas Färber
2009-04-20 14:19       ` Anthony Liguori
2009-04-19 17:42     ` M. Warner Losh
2009-04-20  8:32     ` Avi Kivity
2009-04-20 15:22       ` Blue Swirl
2009-04-20 18:16         ` Avi Kivity
2009-04-19 16:48 ` [Qemu-devel] " Jan Kiszka
2009-04-19 17:41   ` M. Warner Losh
2009-04-20  7:43     ` Jan Kiszka
2009-04-20 14:23     ` Anthony Liguori [this message]
2009-04-19 17:40 ` [Qemu-devel] " M. Warner Losh
2009-04-20 14:13 ` Anthony Liguori
2009-04-20 14:31   ` Avi Kivity
2009-04-20 15:25   ` Blue Swirl
2009-04-20 17:53     ` Anthony Liguori
2009-04-20 14:15 ` Anthony Liguori
2009-04-20 15:29   ` Blue Swirl
2009-04-20 15:53     ` Kevin Wolf
2009-04-20 16:10       ` Blue Swirl
2009-04-20 15:54     ` François Revol
2009-04-20 16:13       ` Avi Kivity
2009-04-20 18:02         ` Anthony Liguori
2009-04-20 18:12           ` Avi Kivity
2009-04-20 17:59       ` Anthony Liguori
2009-04-20 17:56     ` Anthony Liguori

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=49EC8572.9080606@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=jan.kiszka@web.de \
    --cc=qemu-devel@nongnu.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).