On Mon, Sep 15, 2014 at 10:59:01AM +0200, Kevin Wolf wrote:
> Am 15.09.2014 um 03:31 hat Fam Zheng geschrieben:
> > On Sat, 09/13 19:04, Markus Armbruster wrote:
> > I remember at the time of introducing node-name, it was in a separate
> > namespace, but now it's not. Then why should the user care
On Mon, 09/15 10:59, Kevin Wolf wrote:
> Am 15.09.2014 um 03:31 hat Fam Zheng geschrieben:
> > On Sat, 09/13 19:04, Markus Armbruster wrote:
> > >
> > > I actually like having separate parameters for separate kinds of names.
> > >
> > > However, BlockdevRef appears to tie our hand: it's an anon
Am 15.09.2014 um 03:31 hat Fam Zheng geschrieben:
> On Sat, 09/13 19:04, Markus Armbruster wrote:
> >
> > I actually like having separate parameters for separate kinds of names.
> >
> > However, BlockdevRef appears to tie our hand: it's an anonymous union,
> > which means only the value is on t
On Sat, 09/13 19:04, Markus Armbruster wrote:
>
> I actually like having separate parameters for separate kinds of names.
>
> However, BlockdevRef appears to tie our hand: it's an anonymous union,
> which means only the value is on the wire, and the receiving end uses
> its type to determine wh
This has been discussed on IRC, but I want it on the list for further
discussion and later reference.
Terminology: BDS = BlockDriverState, BB = BlockBackend
Traditionally, only root BDSes could be named. They're always uniquely
named; if the user doesn't supply a name via -drive parameter "id",
