From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LvoAP-0006SP-Qt for qemu-devel@nongnu.org; Mon, 20 Apr 2009 03:43:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LvoAL-0006S8-3c for qemu-devel@nongnu.org; Mon, 20 Apr 2009 03:43:49 -0400 Received: from [199.232.76.173] (port=57534 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LvoAK-0006S5-Ti for qemu-devel@nongnu.org; Mon, 20 Apr 2009 03:43:44 -0400 Received: from mx20.gnu.org ([199.232.41.8]:22940) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LvoAK-0004nj-Bi for qemu-devel@nongnu.org; Mon, 20 Apr 2009 03:43:44 -0400 Received: from fmmailgate02.web.de ([217.72.192.227]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LvoAJ-0001xz-7Z for qemu-devel@nongnu.org; Mon, 20 Apr 2009 03:43:43 -0400 Message-ID: <49EC2799.4000805@web.de> Date: Mon, 20 Apr 2009 09:43:21 +0200 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH, RFC] Add file describing rules for submitting patches References: <49EB55D8.7020903@web.de> <20090419.114116.371475325.imp@bsdimp.com> In-Reply-To: <20090419.114116.371475325.imp@bsdimp.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFECF1248A14C898EB27566B2" Sender: jan.kiszka@web.de Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "M. Warner Losh" Cc: qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFECF1248A14C898EB27566B2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable M. Warner Losh wrote: > In message: <49EB55D8.7020903@web.de> > Jan Kiszka writes: > : Blue Swirl wrote: > : > Hi, > : >=20 > : > I gathered a few common complaints about patch submission, hopefull= y > : > not too much affected by my consumption of small amounts of various= > : > alcoholic substances. > :=20 > : Don't drink and patch. Oh, wait, this was: "Don't drink and derive!" = So > : this is probably ok. > :=20 > : >=20 > : > Comments, objections? > :=20 > : SP3.2: If you only attach, pleeeease don't use base64 encoding etc. A= nd > : there should be no maintainer exception... >=20 > How can you attach a patch with MIME and not do that? Mime doesn't imply base64. Binary data enforces base64. Otherwise plain 7bit encoding is fine, and at least my probably rarely used mail client is no longer skeptical about the printability of the attachment. Jan --------------enigFECF1248A14C898EB27566B2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAknsJ5kACgkQniDOoMHTA+msZQCfRiOTXP7HWTBLOyW3zFBZ5KY3 dzwAnAw4BApaQh/4UFVB+Vo6DZZh1ZeG =h436 -----END PGP SIGNATURE----- --------------enigFECF1248A14C898EB27566B2--