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

[Amit Shah <amit.shah@redhat.com>]

On (Thu) Sep 10 2009 [09:56:44], Reimar Döffinger wrote:
> May I repeat my previous question: Is there some CODING file or
> something that has some hints?

There is: CODIING_STYLE.

But that file talks about how to write qemu code.

> If not, would a patch to add such a file be welcome?

Sure.

> 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

Yes

> - Patches should have [PATCH] in subject

Yes

> - 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).

Right; that's what seems to be requested.

> - Patches are preferred inline, even better created by git format-patch
>   (not sure about that either)

This is right too

> - URL of staging tree

Might help; but various developers might have their own staging trees
(as it now is). If things change in the future, this will have to be
modified.

> - Possibly coding style rules once decided (no "pointless" casts of void
>   *)?

That should be covered in CODING_STYLE. The list you're talking about
makes sense for something like SUBMITTING_PATCHES or CONTRIBUTING.

		Amit