From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NG7rK-0007pj-PA
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 04:20:22 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NG7rI-0007p0-Uq
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 04:20:22 -0500
Received: from [199.232.76.173] (port=54477 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NG7rI-0007ol-PH
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 04:20:20 -0500
Received: from afflict.kos.to ([92.243.29.197]:48460)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <nchip@kos.to>) id 1NG7rI-0008Hz-6Z
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 04:20:20 -0500
Date: Thu, 3 Dec 2009 11:20:17 +0200
From: Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] Unclear committer situation
Message-ID: <20091203092017.GA7311@kos.to>
References: <D2A964B8-EC17-4F48-B778-5A6E1F205E3C@suse.de>
	<fb8d4f70912020733h67de2f02o9946dec71a7108b0@mail.gmail.com>
	<4B16B483.6070605@codemonkey.ws>
	<fb8d4f70912021053h3fa79bfdp9e39c5380baeee11@mail.gmail.com>
	<4B16BC1E.5050505@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B16BC1E.5050505@codemonkey.ws>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>, Artyom Tarasenko <atar4qemu@googlemail.com>

On Wed, Dec 02, 2009 at 01:12:30PM -0600, Anthony Liguori wrote:
> Artyom Tarasenko wrote:
>> I thought attaching a second copy were the way to send the patch properly.

> Attaching as an application/octet-stream is not terribly helpful.  It  
> basically means you've attached a binary blob.

>> Is the proper way described somewhere?

> The proper way is to use a mailer that isn't broken.  Attaching  
> everything as "application/octet-stream" is broken.

That should be reported to google.. more and more developers are using gmail
or google hosting for their company mail. Simply switching to another mailer
may not be as easy as it sounds.