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

[Blue Swirl]

On Sun, Sep 13, 2009 at 6:44 PM, Avi Kivity <address@hidden> wrote:
> On 09/12/2009 08:55 AM, Blue Swirl wrote:
>>
>> We had a discussion about this earlier this year:
>> http://lists.gnu.org/archive/html/qemu-devel/2009-04/msg01184.html
>>
>> Since that we have switched to git, so a lot of it could be
>> simplified. Instead of the lengthy formatting specification, we could
>> just require that the patch should apply with "git-am" to git HEAD
>> without any editing, merging or even apply.whitespace=fix.
>>
>
> That doesn't tell people what information to include, and if they don't care
> how the log looks like, they'll do the minimum amount of work to make git am
> like it.

1. Format of e-mail subject
[clip]
SP1.3: The summary must be suitable for changelog as is (start with a
capital letter etc.) after deleting the bracketed text, white space
after it and any text preceding it
[clip]
2. Format of e-mail body
[clip]
SP2.2: The patch description must be selfstanding (not depend on other
patches, other messages or background discussion)

What information should people include? Description of the problem,
step-by-step description how to reproduce it and the solution for the
problem? Brief analysis of the alternative solutions considered so
that if the commit is found buggy, corrective action is easier because
we can try one of the alternatives instead of reverting? Link to
hardware manual chapter where the correct behaviour is described?