From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43930) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZegqY-0001Kz-Pw for qemu-devel@nongnu.org; Wed, 23 Sep 2015 06:00:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZegqT-00072a-7f for qemu-devel@nongnu.org; Wed, 23 Sep 2015 06:00:18 -0400 Received: from mail-wi0-x231.google.com ([2a00:1450:400c:c05::231]:33770) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZegqS-00072U-Sd for qemu-devel@nongnu.org; Wed, 23 Sep 2015 06:00:13 -0400 Received: by wiclk2 with SMTP id lk2so231188590wic.0 for ; Wed, 23 Sep 2015 03:00:12 -0700 (PDT) Sender: Paolo Bonzini References: <1442487809-2403-1-git-send-email-berrange@redhat.com> <20150917120538.GF24971@redhat.com> <20150917123627.GH24971@redhat.com> <87a8slc7yh.fsf@blackfin.pond.sub.org> <56005942.3080301@redhat.com> <871tdqrhqq.fsf@blackfin.pond.sub.org> <5601B6DD.5070508@redhat.com> <8737y5a2dt.fsf@blackfin.pond.sub.org> From: Paolo Bonzini Message-ID: <56027828.2090003@redhat.com> Date: Wed, 23 Sep 2015 12:00:08 +0200 MIME-Version: 1.0 In-Reply-To: <8737y5a2dt.fsf@blackfin.pond.sub.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH] README: fill out some useful quickstart information List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: Peter Maydell , John Snow , QEMU Developers On 23/09/2015 11:52, Markus Armbruster wrote: > > I don't think this is necessary. We should remove duplicate information > > from qemu-doc.texi, developer documentation doesn't belong in manuals. > > Just to avoid misunderstandings: I wouldn't object to splitting > qemu-doc.texi into a user manual and developer documentation. That really boils down to moving chapter 6 somewhere else; everything else is user documentation. I think we should start with Dan's patch, and then integrate it with any missing information from chapter 6. Together with his build system docs, the non-texi developer documentation is better than anything qemu-doc.texi has ever had (*insert usual rant about perfect being the enemy of good*). We also have the opposite problem (user documentation placed in docs/ instead of qemu-doc.texi) but that is separate. Paolo