qemu-stable
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-stable] [PATCH v3 2/2] docs/interop/bitmaps: rewrite and moder


From: John Snow
Subject: Re: [Qemu-stable] [PATCH v3 2/2] docs/interop/bitmaps: rewrite and modernize doc
Date: Tue, 30 Apr 2019 18:56:08 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1


On 4/29/19 9:44 AM, Kashyap Chamarthy wrote:
> On Fri, Apr 26, 2019 at 06:15:28PM -0400, John Snow wrote:
>> This just about rewrites the entirety of the bitmaps.rst document to
>> make it consistent with the 4.0 release. I have added new features seen
>> in the 4.0 release, as well as tried to clarify some points that keep
>> coming up when discussing this feature both in-house and upstream.
>>
>> Yes, it's a lot longer, mostly due to examples. I get a bit chatty.
>> I could use a good editor to help reign in my chattiness.
>>
>> It does not yet cover pull backups or migration details, but I intend to
>> keep extending this document to cover those cases.
>>
>> Please try compiling it with sphinx and look at the rendered output, I
>> don't have hosting to share my copy at present. 
> 
> FWIW, here's a public rendering (with the "Alabaster" Sphinx theme) with
> your v3 applied:
> 
>     
> https://kashyapc.fedorapeople.org/QEMU-Docs-v4.0.0-143-g1cb2ca0415/_build/html/docs/interop/bitmaps.html
> 

Thank you!! We really need to figure out hosting for these.

> Thanks for the overhaul.  Afraid, I've been just too swamped to be able
> to look at this in detail, much as I'd love to.  I will slowly catch up.
> 
>     - - -
> 
> (Note to self: send to the list the text-to-rST converted QEMU docs
> sitting locally on a Git branch.)
> 

PLEASE do! Please CC me on them. I realize it's not a priority for you
at the moment but I will happily take any existing work you've done.

> [...]
> 
>> I think this new layout reads nicer in the HTML format than the old
>> one did, at the expense of looking less readable in the source tree
>> itself (though not completely unmanagable. We did decide to convert it
>> from Markdown to ReST, after all, so I am going all-in on ReST.)
> 
> [...]
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]