From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>, Greg Kurz <groug@kaod.org>
Subject: Re: 9pfs developers docs
Date: Mon, 01 Feb 2021 14:44:50 +0100 [thread overview]
Message-ID: <6582125.VqjDZda3nx@silver> (raw)
In-Reply-To: <CAFEAcA8M29hEVu0XQAk0+fhDsmkDPu7foKAKP75ptEz_KFD+-Q@mail.gmail.com>
On Montag, 1. Februar 2021 12:42:44 CET Peter Maydell wrote:
> On Sun, 31 Jan 2021 at 18:25, Christian Schoenebeck
>
> <qemu_oss@crudebyte.com> wrote:
> > I started setting up some developer documentation for 9pfs:
> > https://wiki.qemu.org/Documentation/9p
> >
> > Still quite a bunch that should be added (e.g. there should be a section
> > about threads and coroutines), but at least it's a start ...
>
> Thanks for working on this; our developer docs of QEMU internals
> are very patchy and improvements and additions to them are very welcome.
>
> The wiki's a good place for initial work on the docs, since it
> allows quick iteration and collaboration. When you think the docs
> are in a more final state you might consider moving them into
> docs/devel/ as an rst file, so they become part of the developer
> manual.
>
> thanks
> -- PMM
I wonder how that is solved on kernel.org, because they also have a wiki and
in-tree rst files. Maybe they have some way to merge content between the two
in a sensible way.
Best regards,
Christian Schoenebeck
prev parent reply other threads:[~2021-02-01 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 18:23 9pfs developers docs Christian Schoenebeck
2021-02-01 9:24 ` Greg Kurz
2021-02-01 11:30 ` Christian Schoenebeck
2021-02-01 12:26 ` Greg Kurz
2021-02-01 13:15 ` Paolo Bonzini
2021-02-01 13:37 ` qemu_oss--- via
2021-02-25 16:31 ` Christian Schoenebeck
2021-02-25 16:47 ` Greg Kurz
2021-02-01 11:42 ` Peter Maydell
2021-02-01 13:44 ` Christian Schoenebeck [this message]
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=6582125.VqjDZda3nx@silver \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).