Am 14.06.2018 um 13:52 hat Markus Armbruster geschrieben:
> Kevin Wolf writes:
>
> > Am 13.06.2018 um 17:23 hat Markus Armbruster geschrieben:
> >> Kevin Wolf writes:
> >>
> >> > Am 12.06.2018 um 14:58 hat Markus Armbruster geschrieben:
> >> >> When you mix scalar and non-scalar keys, whether
Daniel P. Berrangé writes:
> On Thu, Jun 14, 2018 at 10:40:58AM +0200, Kevin Wolf wrote:
>> Am 13.06.2018 um 17:23 hat Markus Armbruster geschrieben:
>> > Kevin Wolf writes:
>> >
>> > > Am 12.06.2018 um 14:58 hat Markus Armbruster geschrieben:
>> > >> When you mix scalar and non-scalar keys,
Kevin Wolf writes:
> Am 13.06.2018 um 17:23 hat Markus Armbruster geschrieben:
>> Kevin Wolf writes:
>>
>> > Am 12.06.2018 um 14:58 hat Markus Armbruster geschrieben:
>> >> When you mix scalar and non-scalar keys, whether you get an "already
>> >> set as scalar" or an "already set as dict"
On Thu, Jun 14, 2018 at 10:40:58AM +0200, Kevin Wolf wrote:
> Am 13.06.2018 um 17:23 hat Markus Armbruster geschrieben:
> > Kevin Wolf writes:
> >
> > > Am 12.06.2018 um 14:58 hat Markus Armbruster geschrieben:
> > >> When you mix scalar and non-scalar keys, whether you get an "already
> > >>
Am 13.06.2018 um 17:23 hat Markus Armbruster geschrieben:
> Kevin Wolf writes:
>
> > Am 12.06.2018 um 14:58 hat Markus Armbruster geschrieben:
> >> When you mix scalar and non-scalar keys, whether you get an "already
> >> set as scalar" or an "already set as dict" error depends on qdict
> >>
Kevin Wolf writes:
> Am 12.06.2018 um 14:58 hat Markus Armbruster geschrieben:
>> When you mix scalar and non-scalar keys, whether you get an "already
>> set as scalar" or an "already set as dict" error depends on qdict
>> iteration order. Neither message makes much sense. Replace by
>>
Am 12.06.2018 um 14:58 hat Markus Armbruster geschrieben:
> When you mix scalar and non-scalar keys, whether you get an "already
> set as scalar" or an "already set as dict" error depends on qdict
> iteration order. Neither message makes much sense. Replace by
> ""Cannot mix scalar and