Re: [Qemu-devel] [PATCH] [RESEND2] Qemu unmaintained?

["Reimar Döffinger" <Reimar.Doeffinger@gmx.de>]

On Thu, Sep 10, 2009 at 12:33:36PM +0530, Amit Shah wrote:
> On (Wed) Sep 09 2009 [08:00:28], Anthony Liguori wrote:
> > Bernhard Kauer wrote:
> >> Its wednesday again, time to resend a patch to the list.
> >> Until today the following happened in this endless story:
> >>   
> >
> > Really, the whining just makes me want to drop your patch..
> 
> Let's be courteous and not drive away contributors.
> 
> There's no relation between accepting patches and some nudging on the
> contributor's part especially when there's no feedback on patches;
> positive or negative.
> 
> If there'd be a daemon sending a mail saying the patch is in some
> staging queue it'll reduce everyone's effort. Such extra mails
> definitely aren't a problem. If it's later reverted because of any kind
> of failure, again a polite mail wouldn't hurt.

May I repeat my previous question: Is there some CODING file or
something that has some hints?
If not, would a patch to add such a file be welcome?
I have the impression that some rules for the Linux kernel development
apply, but I wouldn't know out of my head where to find the guide for
that.
(Things that should be in such a file, at least:
- Patches should be sent to this list
- Patches should have [PATCH] in subject
- Patches should be sent as a new thread even when they are in response
  to some other mail (not sure about that? I didn't really understand
  what that one response I got meant to say, I am just guessing. I also
  think it makes quite a mess for people just reading the list and not
  trying to apply the patches).
- Patches are preferred inline, even better created by git format-patch
  (not sure about that either)
- URL of staging tree
- Possibly coding style rules once decided (no "pointless" casts of void
  *)?
)