From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LvvJz-0001kY-HQ for qemu-devel@nongnu.org; Mon, 20 Apr 2009 11:22:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LvvJu-0001fA-EY for qemu-devel@nongnu.org; Mon, 20 Apr 2009 11:22:10 -0400 Received: from [199.232.76.173] (port=60456 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LvvJt-0001f4-Lt for qemu-devel@nongnu.org; Mon, 20 Apr 2009 11:22:06 -0400 Received: from mx20.gnu.org ([199.232.41.8]:55138) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LvvJt-0007WX-8H for qemu-devel@nongnu.org; Mon, 20 Apr 2009 11:22:05 -0400 Received: from mail-fx0-f169.google.com ([209.85.220.169]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LvvJr-0001vY-85 for qemu-devel@nongnu.org; Mon, 20 Apr 2009 11:22:03 -0400 Received: by fxm17 with SMTP id 17so1799381fxm.34 for ; Mon, 20 Apr 2009 08:22:01 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <49EC3332.8070901@redhat.com> References: <49EB4D42.4050206@redhat.com> <49EC3332.8070901@redhat.com> Date: Mon, 20 Apr 2009 18:22:01 +0300 Message-ID: Subject: Re: [Qemu-devel] [PATCH, RFC] Add file describing rules for submitting patches From: Blue Swirl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 4/20/09, Avi Kivity wrote: > Blue Swirl wrote: > > > > > > > IIRC, one of the requirements is to use your real name :) > > > > > > > > > > I can't find such a requirement :) > > > > > > From [1]: > > > > > then > you just add a line saying > > > > > > > > > Signed-off-by: Random J Developer > > > > > > > > > using your real name (sorry, no pseudonyms or anonymous contributions.) > > OK, I looked at too old version (2.6.16) that had at hand. > > > > > If the patch is attached (and not inlined) it should be marked as > > > text/plain content type. > > > > > > > > > > Added. > > > > > > Your own message has > > --001485f87bbc990faa0467eb577c > Content-Type: plain/text; name="submitting_patches.diff" > Content-Disposition: attachment; > filename="submitting_patches.diff" > Content-Transfer-Encoding: base64 > X-Attachment-Id: f_ftpzesul > > > So my client won't display it inline :) > > A local misconfiguration, or is plain/text legal? I think it's a bug in gmail, I don't know if it can be configured.