From: Luiz Capitulino <lcapitulino@redhat.com>
To: Michal Privoznik <mprivozn@redhat.com>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4] qemu-ga: Add guest-network-info command
Date: Wed, 29 Feb 2012 12:01:16 -0300 [thread overview]
Message-ID: <20120229120116.533bd612@doriath.home> (raw)
In-Reply-To: <4F4E2580.70706@redhat.com>
On Wed, 29 Feb 2012 14:17:52 +0100
Michal Privoznik <mprivozn@redhat.com> wrote:
> On 28.02.2012 18:41, Luiz Capitulino wrote:
> >> Hmm, I know Michal already sent a new version with my suggestions, but
> >> > you're right, splitting out the commands simplified both the responses,
> >> > and makes it easier to discover whether or not that information is
> >> > available, since you can look for the command in guest-info before
> >> > attempting it, rather than attempting it and then looking at the result.
> >> >
> >> > So maybe just something this?:
> >> >
> >> > { 'type': 'GuestNetworkInterface',
> >> > 'data': { 'name': 'str',
> >> > '*hardware-address': 'str',
> >> > '*ip-addresses': ['GuestIpAddress'] } } }
> >> >
> >> > { 'command': 'guest-network-interfaces',
> >> > 'returns': ['GuestNetworkInterface'] }
> > Looks good to me, the only nitpick is that I think command names should be
> > verbs.
>
> guest-get-network-interfaces?
Works for me, but would be good to agree on a standard for it. I'll defer
the decision to Michael, as he's the actual maintainer :)
next prev parent reply other threads:[~2012-02-29 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 11:15 [Qemu-devel] [PATCH v4] qemu-ga: Add guest-network-info command Michal Privoznik
2012-02-22 17:10 ` Michal Privoznik
2012-02-23 14:20 ` Luiz Capitulino
2012-02-27 18:49 ` Michal Privoznik
2012-02-28 2:07 ` Michael Roth
2012-02-28 14:22 ` Luiz Capitulino
2012-02-28 17:09 ` Michael Roth
2012-02-28 17:41 ` Luiz Capitulino
2012-02-29 13:17 ` Michal Privoznik
2012-02-29 15:01 ` Luiz Capitulino [this message]
2012-02-29 15:32 ` Michael Roth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120229120116.533bd612@doriath.home \
--to=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mprivozn@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).