From: xen@bugs.xenproject.org
To: Ian Campbell <Ian.Campbell@citrix.com>, xen-devel@lists.xen.org
Subject: Processed: Re: libxc linux privcmd bugs
Date: Mon, 13 Jan 2014 17:15:02 +0000 [thread overview]
Message-ID: <control-reply-1389633302.28454@bugs.xenproject.org> (raw)
In-Reply-To: <1389632776.13654.108.camel@kazak.uk.xensource.com>
Processing commands for xen@bugs.xenproject.org:
> create ^
Created new bug #34 rooted at `<52D41A0F.5030707@citrix.com>'
Title: `Re: libxc linux privcmd bugs'
> title it libxc should use /dev/xen/privcmd on Linux
Set title for #34 to `libxc should use /dev/xen/privcmd on Linux'
> severity it wishlist
Change severity for #34 to `wishlist'
> thanks
Finished processing.
Modified/created Bugs:
- 34: http://bugs.xenproject.org/xen/bug/34 (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
prev parent reply other threads:[~2014-01-13 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 16:53 libxc linux privcmd bugs Andrew Cooper
2014-01-13 17:06 ` Ian Campbell
2014-01-13 17:06 ` Ian Campbell
2014-01-13 17:15 ` xen [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=control-reply-1389633302.28454@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.