qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] Add file describing rules for 	submitting patches
Date: Mon, 20 Apr 2009 11:32:50 +0300	[thread overview]
Message-ID: <49EC3332.8070901@redhat.com> (raw)
In-Reply-To: <f43fc5580904190959nbd0f92ev6a2932712aab179f@mail.gmail.com>

Blue Swirl wrote:
>> >  IIRC, one of the requirements is to use your real name :)
>>     
>
> I can't find such a requirement :)
>   

 From [1]:

> <http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches;h=f309d3c6221c3699a0c0b97fbe689faed09e4d2f;hb=HEAD#l320>then you just add a line saying
>
> <http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches;h=f309d3c6221c3699a0c0b97fbe689faed09e4d2f;hb=HEAD#l321> 
>
> <http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches;h=f309d3c6221c3699a0c0b97fbe689faed09e4d2f;hb=HEAD#l322>        
> Signed-off-by: Random J Developer <random@developer.example.org>
>
> <http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches;h=f309d3c6221c3699a0c0b97fbe689faed09e4d2f;hb=HEAD#l323> 
>
> <http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches;h=f309d3c6221c3699a0c0b97fbe689faed09e4d2f;hb=HEAD#l324> 
> 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

  parent reply	other threads:[~2009-04-20  8:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 15:32 [Qemu-devel] [PATCH, RFC] Add file describing rules for submitting patches Blue Swirl
2009-04-19 16:11 ` Avi Kivity
2009-04-19 16:59   ` Blue Swirl
2009-04-19 17:36     ` Andreas Färber
2009-04-20 14:19       ` Anthony Liguori
2009-04-19 17:42     ` M. Warner Losh
2009-04-20  8:32     ` Avi Kivity [this message]
2009-04-20 15:22       ` Blue Swirl
2009-04-20 18:16         ` Avi Kivity
2009-04-19 16:48 ` [Qemu-devel] " Jan Kiszka
2009-04-19 17:41   ` M. Warner Losh
2009-04-20  7:43     ` Jan Kiszka
2009-04-20 14:23     ` Anthony Liguori
2009-04-19 17:40 ` [Qemu-devel] " M. Warner Losh
2009-04-20 14:13 ` Anthony Liguori
2009-04-20 14:31   ` Avi Kivity
2009-04-20 15:25   ` Blue Swirl
2009-04-20 17:53     ` Anthony Liguori
2009-04-20 14:15 ` Anthony Liguori
2009-04-20 15:29   ` Blue Swirl
2009-04-20 15:53     ` Kevin Wolf
2009-04-20 16:10       ` Blue Swirl
2009-04-20 15:54     ` François Revol
2009-04-20 16:13       ` Avi Kivity
2009-04-20 18:02         ` Anthony Liguori
2009-04-20 18:12           ` Avi Kivity
2009-04-20 17:59       ` Anthony Liguori
2009-04-20 17:56     ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2009-04-19 21:27 Philippe Waille

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49EC3332.8070901@redhat.com \
    --to=avi@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).