All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH] qemu-options.hx: fix tls-channel help text
Date: Tue, 20 Dec 2011 15:30:46 +0100	[thread overview]
Message-ID: <4EF09C16.8010100@redhat.com> (raw)
In-Reply-To: <1324379118-2570-1-git-send-email-alevy@redhat.com>

On 12/20/11 12:05, Alon Levy wrote:
> Remove the default compiled out tunnel channel, add the always available
> cursor channel. Optimally the man page would depend on compiled in
> options, but that's harder to do.

Acked-by: Gerd Hoffmann <kraxel@redhat.com>

cheers,
  Gerd



WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-options.hx: fix tls-channel help text
Date: Tue, 20 Dec 2011 15:30:46 +0100	[thread overview]
Message-ID: <4EF09C16.8010100@redhat.com> (raw)
In-Reply-To: <1324379118-2570-1-git-send-email-alevy@redhat.com>

On 12/20/11 12:05, Alon Levy wrote:
> Remove the default compiled out tunnel channel, add the always available
> cursor channel. Optimally the man page would depend on compiled in
> options, but that's harder to do.

Acked-by: Gerd Hoffmann <kraxel@redhat.com>

cheers,
  Gerd

  reply	other threads:[~2011-12-20 14:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 11:05 [Qemu-trivial] [PATCH] qemu-options.hx: fix tls-channel help text Alon Levy
2011-12-20 11:05 ` [Qemu-devel] " Alon Levy
2011-12-20 14:30 ` Gerd Hoffmann [this message]
2011-12-20 14:30   ` Gerd Hoffmann
2011-12-21 10:58 ` [Qemu-trivial] " Stefan Hajnoczi
2011-12-21 10:58   ` Stefan Hajnoczi
2011-12-21 10:59 ` [Qemu-trivial] " Stefan Hajnoczi
2011-12-21 10:59   ` Stefan Hajnoczi

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=4EF09C16.8010100@redhat.com \
    --to=kraxel@redhat.com \
    --cc=alevy@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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.