qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: William Dauchy <wdauchy@gmail.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] process naming not working when using a config file
Date: Wed, 2 Apr 2014 19:16:59 +0200	[thread overview]
Message-ID: <CAJ75kXZbNR30nPLRWo_-yB9Xd2H65s3eW2-8DmMB7_vTJgaMWw@mail.gmail.com> (raw)
In-Reply-To: <20140402170505.GO2586@work-vm>

Hello Dave,

Thanks for your quick reply.

On Wed, Apr 2, 2014 at 7:05 PM, Dr. David Alan Gilbert
<dgilbert@redhat.com> wrote:
> You can add a launchpad entry if you like; however sicne I suspect
> it's my rework of --name to use QemuOpts that broke it, I'll add it
> to my list.

If it's already on your todo list, that's ok for me.

Thanks,

-- 
William

      reply	other threads:[~2014-04-02 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 15:50 [Qemu-devel] process naming not working when using a config file William Dauchy
2014-04-02 17:05 ` Dr. David Alan Gilbert
2014-04-02 17:16   ` William Dauchy [this message]

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=CAJ75kXZbNR30nPLRWo_-yB9Xd2H65s3eW2-8DmMB7_vTJgaMWw@mail.gmail.com \
    --to=wdauchy@gmail.com \
    --cc=dgilbert@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).