From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NGCuB-0004RP-JF
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 09:43:40 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NGCu5-0004PV-BA
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 09:43:37 -0500
Received: from [199.232.76.173] (port=50502 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NGCu4-0004PD-UW
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 09:43:33 -0500
Received: from mx1.redhat.com ([209.132.183.28]:7127)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <mst@redhat.com>) id 1NGCu4-0005Mt-M0
	for qemu-devel@nongnu.org; Thu, 03 Dec 2009 09:43:32 -0500
Date: Thu, 3 Dec 2009 16:40:46 +0200
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20091203144046.GA10482@redhat.com>
References: <D2A964B8-EC17-4F48-B778-5A6E1F205E3C@suse.de>
	<fb8d4f70912020733h67de2f02o9946dec71a7108b0@mail.gmail.com>
	<4B16B483.6070605@codemonkey.ws>
	<fb8d4f70912021053h3fa79bfdp9e39c5380baeee11@mail.gmail.com>
	<4B16BC1E.5050505@codemonkey.ws> <4B17B599.6050708@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B17B599.6050708@gmx.net>
Subject: [Qemu-devel] Re: Unclear committer situation
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: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Cc: Artyom Tarasenko <atar4qemu@googlemail.com>, qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>

On Thu, Dec 03, 2009 at 01:56:57PM +0100, Carl-Daniel Hailfinger wrote:
> On 02.12.2009 20:12, 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.
> 
> Some mailers do the right thing if the attachment name ends in .txt
> (maybe that helps with gmail).


linux documentation suggests firefox extension ViewSourceWith.