All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] QMP: Add "Downstream extension of QMP" to spec
Date: Fri, 7 May 2010 16:54:49 -0300	[thread overview]
Message-ID: <20100507165449.1a0d6b38@redhat.com> (raw)
In-Reply-To: <m3zl0cm47d.fsf_-_@blackfin.pond.sub.org>

On Fri, 07 May 2010 11:49:42 +0200
Markus Armbruster <armbru@redhat.com> wrote:

> +Any new names downstream wishes to add must begin with '__'.  To ensure
> +compatibility with other downstreams, it is strongly recommended that
> +you prefix the commands with '__RFQDN_' where RFQDN is a valid, reverse
> +fully qualified domain name which you control.  For example, a qemu-kvm
> +specific monitor command would be:
> +
> +    (qemu) __org.linux-kvm_enable_irqchip

 It's not only for commands, but for async messages and errors as well,
otherwise looks good to me.

  reply	other threads:[~2010-05-07 19:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 20:24 [Qemu-devel] [PATCH] QMP: Spec: Private Extensions support Luiz Capitulino
2010-02-18 21:54 ` Anthony Liguori
2010-02-19 12:04   ` Luiz Capitulino
2010-02-19 13:04   ` Markus Armbruster
2010-02-19 14:01     ` Anthony Liguori
2010-02-22 13:06       ` Markus Armbruster
2010-03-05 19:00   ` Markus Armbruster
2010-03-18 12:36     ` Luiz Capitulino
2010-05-06 15:52     ` Markus Armbruster
2010-05-06 17:49       ` Anthony Liguori
2010-05-07  9:49         ` [Qemu-devel] [PATCH] QMP: Add "Downstream extension of QMP" to spec Markus Armbruster
2010-05-07 19:54           ` Luiz Capitulino [this message]
2010-05-10  7:16             ` [Qemu-devel] [PATCH v2] " Markus Armbruster
2010-05-11 20:01               ` [Qemu-devel] " Luiz Capitulino

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=20100507165449.1a0d6b38@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=armbru@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.