Re: [libvirt] [PATCH v3 02/10] block/dirty-bitmaps: rename frozen predicate helper

2019-02-25 Thread John Snow
On 2/25/19 2:01 AM, Vladimir Sementsov-Ogievskiy wrote: > 23.02.2019 3:06, John Snow wrote: >> "Frozen" was a good description a long time ago, but it isn't adequate now. >> Rename the frozen predicate to has_successor to make the semantics of the >> predicate more clear to outside callers. >>

Re: [libvirt] [PATCH v3 02/10] block/dirty-bitmaps: rename frozen predicate helper

2019-02-24 Thread Vladimir Sementsov-Ogievskiy
23.02.2019 3:06, John Snow wrote: > "Frozen" was a good description a long time ago, but it isn't adequate now. > Rename the frozen predicate to has_successor to make the semantics of the > predicate more clear to outside callers. > > In the process, remove some calls to frozen() that no longer

Re: [libvirt] [PATCH v3 02/10] block/dirty-bitmaps: rename frozen predicate helper

2019-02-23 Thread Eric Blake
On 2/22/19 6:06 PM, John Snow wrote: > "Frozen" was a good description a long time ago, but it isn't adequate now. > Rename the frozen predicate to has_successor to make the semantics of the > predicate more clear to outside callers. > > In the process, remove some calls to frozen() that no

[libvirt] [PATCH v3 02/10] block/dirty-bitmaps: rename frozen predicate helper

2019-02-22 Thread John Snow
"Frozen" was a good description a long time ago, but it isn't adequate now. Rename the frozen predicate to has_successor to make the semantics of the predicate more clear to outside callers. In the process, remove some calls to frozen() that no longer semantically make sense. For