qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kashyap Chamarthy <kchamart@redhat.com>
To: "Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>
Cc: pbonzini@redhat.com, thuth@redhat.com, eblake@redhat.com,
	qemu-devel@nongnu.org, peter.maydell@linaro.org
Subject: Re: [PATCH v2 2/3] docs: rSTify MailingLists wiki; move it to QEMU Git
Date: Mon, 14 Mar 2022 16:10:49 +0100	[thread overview]
Message-ID: <Yi9a+cA5lO+tUfIu@paraplu> (raw)
In-Reply-To: <a87fc975-ff3b-f7a3-0bb4-9791f2ff3437@gmail.com>

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	other threads:[~2022-03-14 15:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 10:49 [PATCH v2 0/3] rSTify a few more docs; move them to QEMU Git Kashyap Chamarthy
2022-03-14 10:49 ` [PATCH v2 1/3] docs: rSTify "security-process" page; move it " Kashyap Chamarthy
2022-03-15 12:47   ` Thomas Huth
2022-03-15 13:42     ` Kashyap Chamarthy
2022-03-14 10:49 ` [PATCH v2 2/3] docs: rSTify MailingLists wiki; " Kashyap Chamarthy
2022-03-14 13:45   ` Philippe Mathieu-Daudé
2022-03-14 15:10     ` Kashyap Chamarthy [this message]
2022-03-15 13:25   ` Thomas Huth
2022-03-15 16:00     ` Kashyap Chamarthy
2022-03-15 16:12       ` Peter Maydell
2022-03-21  9:55         ` Kashyap Chamarthy
2022-03-21 11:01           ` Peter Maydell
2022-03-21 11:18             ` Kashyap Chamarthy
2022-03-14 10:49 ` [PATCH v2 3/3] docs: rSTify GettingStartedDevelopers " Kashyap Chamarthy

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=Yi9a+cA5lO+tUfIu@paraplu \
    --to=kchamart@redhat.com \
    --cc=eblake@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philippe.mathieu.daude@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).