From: xen@bugs.xenproject.org
To: Ian Campbell <Ian.Campbell@citrix.com>, xen-devel@lists.xen.org
Subject: Processed: Re: [Xen-users] XEN 4.3.1 VNC TLS is not working?
Date: Tue, 26 Nov 2013 10:45:03 +0000 [thread overview]
Message-ID: <control-reply-1385462703.14623@bugs.xenproject.org> (raw)
In-Reply-To: <1385462142.23112.11.camel@kazak.uk.xensource.com>
Processing commands for xen@bugs.xenproject.org:
> create !
Created new bug #24 rooted at `<1385462142.23112.11.camel@kazak.uk.xensource.com>'
Title: `Re: [Xen-users] XEN 4.3.1 VNC TLS is not working?'
> title it xl missing support for encrypted VNC
Set title for #24 to `xl missing support for encrypted VNC'
> thanks
Finished processing.
Modified/created Bugs:
- 24: http://bugs.xenproject.org/xen/bug/24 (new)
---
Xen Hypervisor Bug Tracker
See http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen for information on reporting bugs
Contact xen-bugs-owner@bugs.xenproject.org with any infrastructure issues
next prev parent reply other threads:[~2013-11-26 10:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <176b55e39d32473c9f9df0b78ee6debe.squirrel@gameframe.net>
[not found] ` <20131125182145.GA12187@zion.uk.xensource.com>
[not found] ` <9295e78bd3e92a206a60699d47f93fa8.squirrel@gameframe.net>
[not found] ` <20131125191555.GA14643@zion.uk.xensource.com>
[not found] ` <7af405967c3e9400a048590dd0ab411a.squirrel@gameframe.net>
[not found] ` <20131125215950.GB14643@zion.uk.xensource.com>
[not found] ` <5e56a8c32e6e9d96b56eb42a738a5f8a.squirrel@gameframe.net>
[not found] ` <20131125225422.GC14643@zion.uk.xensource.com>
[not found] ` <1385461248.20703.29.camel@kazak.uk.xensource.com>
2013-11-26 10:35 ` [Xen-users] XEN 4.3.1 VNC TLS is not working? Ian Campbell
2013-11-26 10:45 ` xen [this message]
2014-06-05 18:36 ` Robby
2014-06-05 18:53 ` Wei Liu
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=control-reply-1385462703.14623@bugs.xenproject.org \
--to=xen@bugs.xenproject.org \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xen.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.