From: Kashyap Chamarthy <kchamart@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: pbonzini@redhat.com, Thomas Huth <thuth@redhat.com>,
eblake@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 2/3] docs: rSTify MailingLists wiki; move it to QEMU Git
Date: Mon, 21 Mar 2022 10:55:05 +0100 [thread overview]
Message-ID: <YjhLeU8sIIMAwUK+@paraplu> (raw)
In-Reply-To: <CAFEAcA9vqS+2Tou1iK7hqmFXnvsXxABmYW9EQRjGnKKAp=k_xQ@mail.gmail.com>
On Tue, Mar 15, 2022 at 04:12:50PM +0000, Peter Maydell wrote:
> On Tue, 15 Mar 2022 at 16:00, Kashyap Chamarthy <kchamart@redhat.com> wrote:
> >
> > On Tue, Mar 15, 2022 at 02:25:05PM +0100, Thomas Huth wrote:
> > > On 14/03/2022 11.49, Kashyap Chamarthy wrote:
> >
> > [...]
> >
> > > At least the "users" mailing list is not related to development, so maybe
> > > this should rather go into docs/about/ instead?
> >
> > Yeah, makes sense. I wonder if should create a new doc in docs/about/
> > for user-lists, as none of the existing docs fit the bill:
> >
> > build-platforms.rst deprecated.rst index.rst license.rst
> > removed-features.rst
>
> Yes, I think that about/ should have a document something like
> "Contacting the project" or "Support", which could tell users about not just
> the user-facing mailing lists but also where to file bugs, and so on.
>
> In fact, it should probably look rather like the
> https://www.qemu.org/support/ page...
Heh, thanks, I missed that page. So, if I parsed you right, you're
implying, given the above qemu-web page, there's no need for a separate
about/support.rst doc.
--
/kashyap
next prev parent reply other threads:[~2022-03-21 9:56 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
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 [this message]
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=YjhLeU8sIIMAwUK+@paraplu \
--to=kchamart@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).