From: Kashyap Chamarthy <kchamart@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH] docs: Convert migration.txt to rst
Date: Thu, 14 Dec 2017 12:26:03 +0100 [thread overview]
Message-ID: <20171214112603.7gkt3dwgxoioybse@eukaryote> (raw)
In-Reply-To: <20171213201145.GB8501@work-vm>
On Wed, Dec 13, 2017 at 08:11:46PM +0000, Dr. David Alan Gilbert wrote:
> * Kashyap Chamarthy (kchamart@redhat.com) wrote:
> > On Tue, Dec 12, 2017 at 01:56:00PM +0000, Dr. David Alan Gilbert (git) wrote:
[...]
> > A good chunk of changes I suggest are pre-existing, so take it with a
> > grain of salt :-). I'm ambivalent on whether to keep the conversion to
> > rST and the other rST syntax changes separate. Maybe we can keep in one
> > change, as this doesn't impact backports in terms of code /
> > functionality.
>
> I'd like to fix the non-rST fixes some other time; there's plenty wrong
> with the actual contents of this file.
That's fine.
> (I need to pull in a fix from Jay Zhou before resending this actually).
[...]
> > Not this patch's problem, but do we have the more information that is to
> > be filled in above?
>
> Oh yes, plenty!
Okay, I take it that you'd address them as a future patch.
[...]
> > - I think the above is a TODO item; so you can use:
> >
> > .. TODO (dgilbert):: talk about how vmstate <-> qdev interact, and
> > what the instance ids mean.
> >
> > As that'll keep it only in the source rST; but not in the rendered
> > version.
>
> I'd rather leave the items rendered, otherwise they have even less
> chance of being fixed.
Yeah, I thought about it too; you're correct, a visual reminder works
better.
[...]
> > > When postcopy starts the source sends the page discard data and then
> > > forms the 'package' containing:
> > >
> > > - Command: 'postcopy listen'
> > > - The device state
> >
> > In my local Sphinx-based HTML rendering, the above "The device state"
> > ended up being bold somehow.
>
> Any idea why? It's fine both in vim and rst2html-3's output.
Don't know yet. You can see here in the Sphinx-rendered HTML version:
https://kashyapc.fedorapeople.org/QEMU-Docs/_build/html/docs/migration.html
You can also see in the "Massaging functions" --> "Subsections" --> "For
example;" also turned into bold.
Same for the "Postcopy states". And a couple of other places, where
text turned into bold.
I'll let you know once I figure it out.
[...]
--
/kashyap
next prev parent reply other threads:[~2017-12-14 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 13:56 [Qemu-devel] [PATCH] docs: Convert migration.txt to rst Dr. David Alan Gilbert (git)
2017-12-12 15:10 ` Peter Xu
2017-12-13 19:49 ` Dr. David Alan Gilbert
2017-12-12 18:23 ` Kashyap Chamarthy
2017-12-13 20:11 ` Dr. David Alan Gilbert
2017-12-14 11:26 ` Kashyap Chamarthy [this message]
2017-12-14 17:18 ` Kashyap Chamarthy
2017-12-14 18:09 ` Dr. David Alan Gilbert
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=20171214112603.7gkt3dwgxoioybse@eukaryote \
--to=kchamart@redhat.com \
--cc=dgilbert@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).