From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lvow2-000848-Gc for qemu-devel@nongnu.org; Mon, 20 Apr 2009 04:33:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lvovw-0007yL-8p for qemu-devel@nongnu.org; Mon, 20 Apr 2009 04:33:01 -0400 Received: from [199.232.76.173] (port=43919 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lvovw-0007y3-2l for qemu-devel@nongnu.org; Mon, 20 Apr 2009 04:32:56 -0400 Received: from mx2.redhat.com ([66.187.237.31]:58833) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lvovv-0003SR-7C for qemu-devel@nongnu.org; Mon, 20 Apr 2009 04:32:55 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n3K8WrGS025861 for ; Mon, 20 Apr 2009 04:32:53 -0400 Message-ID: <49EC3332.8070901@redhat.com> Date: Mon, 20 Apr 2009 11:32:50 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH, RFC] Add file describing rules for submitting patches References: <49EB4D42.4050206@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed 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 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.) >> 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? >> Suggest instead: patches should state which branch they are based on, and >> should be based on a recent version of the branch. >> > > I'd suppose most of the patches are for the development branch, so one > of the subject tags could be "STABLE" indicating stable branch. > Without it dev branch is assumed. > Right. [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches;h=f309d3c6221c3699a0c0b97fbe689faed09e4d2f;hb=HEAD -- error compiling committee.c: too many arguments to function