On 09/12/14 23:30, Eric Blake wrote:
[revisiting something that finally surfaced to the top of my todo list]
On 08/07/2014 03:57 AM, Peter Krempa wrote:
On 08/06/14 18:36, Eric Blake wrote:
Adam Litke has been asking if I can expose watermark information from\
bikeshedding
I'd be glad if
On 16/09/14 09:29 +0200, Peter Krempa wrote:
On 09/12/14 23:30, Eric Blake wrote:
[revisiting something that finally surfaced to the top of my todo list]
On 08/07/2014 03:57 AM, Peter Krempa wrote:
On 08/06/14 18:36, Eric Blake wrote:
Adam Litke has been asking if I can expose watermark
[revisiting something that finally surfaced to the top of my todo list]
On 08/07/2014 03:57 AM, Peter Krempa wrote:
On 08/06/14 18:36, Eric Blake wrote:
Adam Litke has been asking if I can expose watermark information from\
bikeshedding
I'd be glad if we stopped calling this watermark. The
On 08/06/14 18:36, Eric Blake wrote:
Adam Litke has been asking if I can expose watermark information from\
bikeshedding
I'd be glad if we stopped calling this watermark. The wiki
disambiguation article states:
citation
A watermark is a recognizable image or pattern in paper used to identify
Adam Litke has been asking if I can expose watermark information from
qemu when doing block commit. Qemu still doesn't expose that
information when doing 'virsh blockcopy' (QMP drive-mirror), but DOES
expose it for regular and active 'virsh blockcommit'. The idea is that
when you are writing to
On 06/08/14 10:36 -0600, Eric Blake wrote:
Adam Litke has been asking if I can expose watermark information from
qemu when doing block commit. Qemu still doesn't expose that
information when doing 'virsh blockcopy' (QMP drive-mirror), but DOES
expose it for regular and active 'virsh
