20.06.2019 19:47, Max Reitz wrote:
> On 20.06.19 03:03, John Snow wrote:
>> Signed-off-by: John Snow
>> ---
>> util/hbitmap.c | 22 +-
>> 1 file changed, 21 insertions(+), 1 deletion(-)
>
> I wonder whether this could be used in
> backup_incremental_init_copy_bitmap(). The
20.06.2019 4:03, John Snow wrote:
> Signed-off-by: John Snow
> ---
> util/hbitmap.c | 22 +-
> 1 file changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/util/hbitmap.c b/util/hbitmap.c
> index 45d1725daf..0d6724b7bc 100644
> --- a/util/hbitmap.c
> +++ b/util/hbitmap.
On 6/20/19 11:47 AM, Max Reitz wrote:
> On 20.06.19 03:03, John Snow wrote:
>> Signed-off-by: John Snow
>> ---
>> util/hbitmap.c | 22 +-
>> 1 file changed, 21 insertions(+), 1 deletion(-)
>>
>> diff --git a/util/hbitmap.c b/util/hbitmap.c
>> index 45d1725daf..0d6724b7bc 10
On 20.06.19 03:03, John Snow wrote:
> Signed-off-by: John Snow
> ---
> util/hbitmap.c | 22 +-
> 1 file changed, 21 insertions(+), 1 deletion(-)
I wonder whether this could be used in
backup_incremental_init_copy_bitmap(). The sync_bitmap must have the
same length as the sou
On 20.06.19 03:03, John Snow wrote:
> Signed-off-by: John Snow
> ---
> util/hbitmap.c | 22 +-
> 1 file changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/util/hbitmap.c b/util/hbitmap.c
> index 45d1725daf..0d6724b7bc 100644
> --- a/util/hbitmap.c
> +++ b/util/hbitmap.
Signed-off-by: John Snow
---
util/hbitmap.c | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/util/hbitmap.c b/util/hbitmap.c
index 45d1725daf..0d6724b7bc 100644
--- a/util/hbitmap.c
+++ b/util/hbitmap.c
@@ -777,7 +777,17 @@ void hbitmap_truncate(HBitmap *