From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] Add file describing rules for submitting patches
Date: Sun, 19 Apr 2009 19:59:51 +0300 [thread overview]
Message-ID: <f43fc5580904190959nbd0f92ev6a2932712aab179f@mail.gmail.com> (raw)
In-Reply-To: <49EB4D42.4050206@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]
On 4/19/09, Avi Kivity <avi@redhat.com> wrote:
> Blue Swirl wrote:
>
> > Hi,
> >
> > I gathered a few common complaints about patch submission, hopefully
> > not too much affected by my consumption of small amounts of various
> > alcoholic substances.
> >
> > +
> > +SP2.3: The description must be followed by one blank line and a
> > +"Signed-off-by:" line
> >
>
> A signoff is more than a format; it is a legal declaration, see the Linux
> Documentation/SubmittingPatches. It should be clear to the
> submitter that this is so.
I added this to a new section together with the licensing stuff.
> IIRC, one of the requirements is to use your real name :)
I can't find such a requirement :)
> > +
> > +SP3.2: If possible, please send the patch inlined (to make commenting
> > +easier) and also attached (to make it easier to apply)
> >
>
> If the patch is attached (and not inlined) it should be marked as
> text/plain content type.
Added.
> > +
> > +SP4.4: The patches targeted for development branch must be based on
> > +the current development repository
> > +
> > +SP4.5: The patches targeted for stable branch must be based on the
> > +current stable repository
> >
>
> 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.
> In addition:
>
> When sending multiple patches, patches should be numbered (inside the
> brackets: [PATCH 09/17]) and should include a cover letter describing the
> patchset in general (as opposed to infividual patch descriptions). Patch
> management utilities (git send-email, quilt, and similar) can do this, so
> their use is recommended.
I collected the patch series stuff to a new section.
[-- Attachment #2: submitting_patches.diff --]
[-- Type: plain/text, Size: 4826 bytes --]
next prev parent reply other threads:[~2009-04-19 16:59 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 [this message]
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
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=f43fc5580904190959nbd0f92ev6a2932712aab179f@mail.gmail.com \
--to=blauwirbel@gmail.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).