qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, qemu-block@nongnu.org,
	stephen@that.guru, armbru@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3] live-block-ops.txt: Rename, rewrite, and improve it
Date: Thu, 22 Jun 2017 10:13:03 -0400	[thread overview]
Message-ID: <3e638f0a-49f8-6fd0-04eb-12904768d571@redhat.com> (raw)
In-Reply-To: <20170622085610.wasfoafo3b46iv4q@eukaryote>



On 06/22/2017 04:56 AM, Kashyap Chamarthy wrote:
> On Wed, Jun 21, 2017 at 06:49:02PM -0400, John Snow wrote:
> 
> [...]
> 
>>> * TODO (after feedback from John Snow):
>>>    - Eric Blake suggested to consider documenting incremental backup
>>>      policies as part of the section: "Live disk backup ---
>>>      `drive-backup` and `blockdev-backup`"
>>
>> Perhaps it could be mentioned, but hopefully I've covered it in some
>> sufficient detail in the (now) docs/devel/bitmaps.md file; 
> 
> Yes, that doc is very useful.  That was my precise thought.
> 
>> I'm a little wary of duplicating efforts in this area, 
> 
> I share your wariness.
> 
>> but you've covered everything *else* in good detail here, so now my
>> file is the odd one out.
>>
>> I will leave this up to you, really. Perhaps it could be paid some lip
>> service with a link to the other document? 
> 
> Yes, I was thinking of this, too -- just link to the 'bitmaps' document.
> 
> A quick side question here: Since upstream QEMU is converging onto
> Sphinx, and rST, hope you mind if I convert docs/devel/bitmaps.md into
> rST at somepoint, for consistency's sake.  I'll file a separate review,
> anyway for that.  In the long term, all / most other documents would
> also be converted.
> 

Of course not. I chose bitmaps.md so that it would be nice to view from
the github interface while remaining nice to read in plaintext, but feel
free to convert it if we actually do standardize on Sphinx/rST.

If you can make the generated output look prettier than the github
rendering of the markdown I'll ACK it ;)

>> The detail in bitmaps.md is a little more verbose than the rest of
>> this file, so if you include it wholesale it'd dwarf the rest of this
>> document.
>>
>> What do you think?
> 
> Yes, I fully agree with your suggestion.  I will simply link to the
> detailed document you wrote, which I was thinking of anyhow.
> 
> Thanks for your comments!
> 
Sure. You could perhaps mention the different sync modes, including top,
none, full and incremental and urge readers to check out the bitmaps
document for detailed workings of the incremental mode.

  reply	other threads:[~2017-06-22 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 10:19 [Qemu-devel] [PATCH v3] live-block-ops.txt: Rename, rewrite, and improve it Kashyap Chamarthy
2017-06-21 22:49 ` John Snow
2017-06-22  8:56   ` Kashyap Chamarthy
2017-06-22 14:13     ` John Snow [this message]
2017-06-23  8:15       ` Kashyap Chamarthy
2017-06-23 18:53         ` John Snow

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=3e638f0a-49f8-6fd0-04eb-12904768d571@redhat.com \
    --to=jsnow@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stephen@that.guru \
    /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).