All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Waille <Philippe.Waille@imag.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] Add file describing rules for submitting patches
Date: Sun, 19 Apr 2009 23:27:38 +0200	[thread overview]
Message-ID: <20090419212738.GA7868@otto.imag.fr> (raw)

Blue Swirl wrote :

> I gathered a few common complaints about patch submission,
> ...

A newbie remark : what is needed IMHO is a clear and complete documentation on how 
to submit a patch, at the top-level QEMU WEB page and within the tar archive. 

I tried to submit a patch (for the user mode gdbstub) and the only information I got
on the QEMU WEB site on how to proceed is :

"The prefered way to submit QEMU Patches is to send them to QEMU developer
mailing list".  


A look at already submitted submitted and applied patch submission messages in
the qemu-devel archive help to guess what is required, but the following informations 
should IHMO be clearly explained in a document "HOW to submit a patch" :

+ format (guessed svn diff)
+ inclusion (in-line or attachement, format of attachement), which files
(diff only, diff + modified files ... ?)
+ subject Line rules 
+ signature : how to sign a path submission (with a PGP key ? how to get this key ?)

If appropriate, add a link to a more general (GNU projects) patch submission policy and 
variations specific to QEMU project. 



And I can't find again the QEMU coding style document today (but the
QEMU users forum link is broken ...).

Ph. Waille

             reply	other threads:[~2009-04-19 21:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 21:27 Philippe Waille [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2009-04-20 15:22       ` Blue Swirl
2009-04-20 18:16         ` Avi Kivity
2009-04-19 17:40 ` 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

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=20090419212738.GA7868@otto.imag.fr \
    --to=philippe.waille@imag.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.