From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Scott Wood <scottwood@freescale.com>,
Blue Swirl <blauwirbel@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-trivial <qemu-trivial@nongnu.org>,
Stefan Hajnoczi <stefanha@gmail.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-ppc <qemu-ppc@nongnu.org>, Hu Tao <hutao@cn.fujitsu.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] ANN: DeveloperNews - a qemu-devel digest for maintainers and contributors
Date: Sat, 06 Jul 2013 01:26:52 +0200 [thread overview]
Message-ID: <51D7563C.90000@suse.de> (raw)
Hello everyone,
Inspired by a complaint from Scott about information getting lost
amongst qemu-devel mails, and spawning a qemu-announce mailing list
being out of my powers, I have started a simple Wiki page:
http://wiki.qemu.org/DeveloperNews
The idea is to have a brief summary of decisions and code changes that
affect all maintainers and/or contributors, with references into
qemu-devel archive or git.qemu.org or developers' blogs for more info,
latest news sorted first.
For example, to aid in getting up to speed after a four-week vacation,
and to aid hobbyists in coping with the sheer incredible list volume.
Self-explanatory that this will only work when information there is less
than on qemu-devel (i.e., not every PULL or patchset linked).
The intended scope is not random news about what changed in qemu.git but
code changes that require fellow developers to rebase or to adopt new
patterns and conventions and review criteria. The removal of some
function does not necessarily need to be documented there (anyone
building against latest master would notice a breakage) but whenever
there's old and new ways to do things, we can advise which to choose.
The initial contents is of course biased to what's close to my heart;
but it's a Wiki, so for instance Stefan H. could add a bullet point
about new devices please using new asynchronous block layer APIs only.
Obviously adding Wiki contents is work, it cannot replace cover letters
or commit messages, but after the n-th reply pages like SubmitAPatch or
QOMConventions have become very handy to refer to.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
reply other threads:[~2013-07-05 23:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51D7563C.90000@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=hutao@cn.fujitsu.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=scottwood@freescale.com \
--cc=stefanha@gmail.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).