qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2 2/3] docs: rSTify MailingLists wiki; move it to QEMU Git


From: Kashyap Chamarthy
Subject: Re: [PATCH v2 2/3] docs: rSTify MailingLists wiki; move it to QEMU Git
Date: Mon, 14 Mar 2022 16:10:49 +0100

On Mon, Mar 14, 2022 at 02:45:30PM +0100, Philippe Mathieu-Daudé wrote:
> Hi Kashyap,

Hi,

> On 14/3/22 11:49, Kashyap Chamarthy wrote:

[...]

> This is a fair conversion from
> https://wiki.qemu.org/Contribute/MailingLists, but a good opportunity to
> improve (could be on top).

Yeah, definitely.  I'll make a TODO to add it on top.  (I didn't wanted
to mix in content edits with conversion changes, as it puts additional
burden on the reviewers.)

> We could sort as:
> 
>  * qemu-discuss
> 
>    Meant for users. Ideally help should point at Documentation link,
>    and in case of missing doc we should add it or at least a GitLab
>    @Documentation ticket.
> 
>  * qemu-devel
> 
>    Meant for developers. "All patches must be sent there".
> 
>    Then developer sub-lists:
> 
>    - qemu-trivial
> 
>    - qemu-stable (this is kinda borderline, security issue fixes should
>      Cc this list, however it has to be treated as a write-only list
>      - a way to tag patches - no discussion happens there).

Nit: The term "kinda boderline" here can mean anything from "its
purpose is questionable" to "it is used for unintended purposes", etc.
Let's avoid vague phrasing in public-facing text.  We can just be
descriptive of what the purpose of the list is. :-)

Thanks for the review!

>    - susbsystem specific
> 
>      > block layer
> 
>      > architecture specific
> 
>        . ARM
>        . PPC
>        . ...

[...]


-- 
/kashyap




reply via email to

[Prev in Thread] Current Thread [Next in Thread]