On Tue, May 30, 2017 at 03:42:08PM -0500, Eric Blake wrote:
> On 05/30/2017 03:24 PM, Kashyap Chamarthy wrote:
[...]
> > Eric, do you have an opinion: Now that I _do_ have the notes
> > available[*], do you think it is worth spelling out the invocation for
> > QMP `blockdev-{backup, mirror}`? O
On 05/30/2017 03:24 PM, Kashyap Chamarthy wrote:
> First, thanks for the quick feedback!
>
> On Tue, May 30, 2017 at 02:24:40PM -0500, Eric Blake wrote:
>> On 05/30/2017 10:38 AM, Kashyap Chamarthy wrote:
>>> This edition documents all four operations:
>
>>> +
>>> +(1) `Disk image backing chain
First, thanks for the quick feedback!
On Tue, May 30, 2017 at 02:24:40PM -0500, Eric Blake wrote:
> On 05/30/2017 10:38 AM, Kashyap Chamarthy wrote:
> > This edition documents all four operations:
[...]
> s/occurance/occurrence/
>
> > use raw JSON; for subsequent occurances, use 'qmp-shell'
On 05/30/2017 10:38 AM, Kashyap Chamarthy wrote:
> This edition documents all four operations:
>
> - `block-stream`
> - `block-commit`
> - `drive-mirror` (& `blockdev-mirror`)
> - `drive-backup` (& `blockdev-backup`)
>
> Things considered while writing this document:
>
> - Use reStruct
This edition documents all four operations:
- `block-stream`
- `block-commit`
- `drive-mirror` (& `blockdev-mirror`)
- `drive-backup` (& `blockdev-backup`)
Things considered while writing this document:
- Use reStructuredText format. It is gentler on the eye, and can be
trivially
This edition documents all four operations:
- `block-stream`
- `block-commit`
- `drive-mirror` (& `blockdev-mirror`)
- `drive-backup` (& `blockdev-backup`)
Things considered while writing this document:
- Use reStructuredText format. It is gentler on the eye, and can be
trivially
