qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Stefan Hajnoczi" <stefanha@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Eduardo Otubo" <otubo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] security.rst: add Security Guide to developer docs
Date: Fri, 3 May 2019 11:35:29 +0100	[thread overview]
Message-ID: <20190503103529.GD17905@redhat.com> (raw)
In-Reply-To: <CAFEAcA_CkUBHe1fWg9wy-+HLw8WBZrp3M_oBksCN1GQc1qp4hg@mail.gmail.com>

On Fri, May 03, 2019 at 11:28:53AM +0100, Peter Maydell wrote:
> On Fri, 3 May 2019 at 11:19, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > Everything above here is useful to QEMU devs, app devs & end users and
> > should be made part of the main QEMU doc - convert it to texi and @include
> > it from qemu-doc.texi, as we do for other stuff under docs/
> 
> If we convert it to texi we'll have to convert it back again
> as/when we migrate properly from texi to sphinx... (I would
> like to make further moves in that direction during this
> release cycle -- just need to find the time to work on it.)

Yes, but we're only talking about 100-150 lines of simple text with
minimal markup needs. Won't be a noticable extra burden compared to
the pre-existing 4700 lines of texi markup for qemu-doc.texi and its
includes.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Eduardo Otubo" <otubo@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] security.rst: add Security Guide to developer docs
Date: Fri, 3 May 2019 11:35:29 +0100	[thread overview]
Message-ID: <20190503103529.GD17905@redhat.com> (raw)
Message-ID: <20190503103529.F-DYo-QtMdgCkxosT183i_PF8zwPKjo8RfhkHbWGQg8@z> (raw)
In-Reply-To: <CAFEAcA_CkUBHe1fWg9wy-+HLw8WBZrp3M_oBksCN1GQc1qp4hg@mail.gmail.com>

On Fri, May 03, 2019 at 11:28:53AM +0100, Peter Maydell wrote:
> On Fri, 3 May 2019 at 11:19, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > Everything above here is useful to QEMU devs, app devs & end users and
> > should be made part of the main QEMU doc - convert it to texi and @include
> > it from qemu-doc.texi, as we do for other stuff under docs/
> 
> If we convert it to texi we'll have to convert it back again
> as/when we migrate properly from texi to sphinx... (I would
> like to make further moves in that direction during this
> release cycle -- just need to find the time to work on it.)

Yes, but we're only talking about 100-150 lines of simple text with
minimal markup needs. Won't be a noticable extra burden compared to
the pre-existing 4700 lines of texi markup for qemu-doc.texi and its
includes.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|


  parent reply	other threads:[~2019-05-03 10:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 13:35 [Qemu-devel] [PATCH v2] security.rst: add Security Guide to developer docs Stefan Hajnoczi
2019-04-25 13:35 ` Stefan Hajnoczi
2019-05-01 16:20 ` Stefan Hajnoczi
2019-05-01 16:20   ` Stefan Hajnoczi
2019-05-03  8:14 ` Stefano Garzarella
2019-05-03  8:14   ` Stefano Garzarella
2019-05-03  9:04 ` Alex Bennée
2019-05-03  9:04   ` Alex Bennée
2019-05-03 10:10   ` Philippe Mathieu-Daudé
2019-05-03 10:10     ` Philippe Mathieu-Daudé
2019-05-03 17:32   ` Stefan Hajnoczi
2019-05-03 17:32     ` Stefan Hajnoczi
2019-05-03 10:19 ` Daniel P. Berrangé
2019-05-03 10:19   ` Daniel P. Berrangé
2019-05-03 10:28   ` Peter Maydell
2019-05-03 10:28     ` Peter Maydell
2019-05-03 10:35     ` Daniel P. Berrangé [this message]
2019-05-03 10:35       ` Daniel P. Berrangé
2019-05-03 17:30       ` Stefan Hajnoczi
2019-05-03 17:30         ` Stefan Hajnoczi

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=20190503103529.GD17905@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=otubo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).