From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50175) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UvFP5-0000nG-Jg for qemu-devel@nongnu.org; Fri, 05 Jul 2013 19:27:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UvFP1-0005ji-UV for qemu-devel@nongnu.org; Fri, 05 Jul 2013 19:27:03 -0400 Message-ID: <51D7563C.90000@suse.de> Date: Sat, 06 Jul 2013 01:26:52 +0200 From: =?ISO-8859-15?Q?Andreas_F=E4rber?= MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] ANN: DeveloperNews - a qemu-devel digest for maintainers and contributors List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel , Anthony Liguori , Scott Wood , Blue Swirl Cc: Peter Maydell , "Michael S. Tsirkin" , qemu-trivial , Stefan Hajnoczi , "Edgar E. Iglesias" , qemu-ppc , Hu Tao , Paolo Bonzini , Aurelien Jarno 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 --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg