All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Lars Kurth <lars.kurth.xen@gmail.com>
Cc: keir@xen.org, Tim Deegan <tim@xen.org>,
	Ian.Jackson@eu.citrix.com, Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xenproject.org
Subject: Re: Formal Vote for changes to Xen Project Security Policy encoded in [PATCH v2 SECURITY-POLICY */9] (vote ends next Wed, Feb 11th)
Date: Tue, 22 Sep 2015 13:29:10 +0100	[thread overview]
Message-ID: <1442924950.10338.157.camel@citrix.com> (raw)
In-Reply-To: <5F1ACAD6-B9DC-45D0-9F09-E2EEDD27D980@gmail.com>

close 44
thanks

On Tue, 2015-09-22 at 13:12 +0100, Lars Kurth wrote:
> Folks,
> this bug should probably be closed.

I think you meant #44. I've closed that here.

Anyone can close any bug, no special privilege is required

See http://wiki.xen.org/wiki/Xen_Bug_Management_Interface.

Ian.

  reply	other threads:[~2015-09-22 12:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 12:12 Formal Vote for changes to Xen Project Security Policy encoded in [PATCH v2 SECURITY-POLICY */9] (vote ends next Wed, Feb 11th) Lars Kurth
2015-09-22 12:29 ` Ian Campbell [this message]
2015-09-22 12:45   ` Processed: " xen
  -- strict thread matches above, loose matches on Subject: below --
2015-01-29 12:16 Vote for Xen 4.6 Release Manager (vote ends next Thu, Feb 4th) Konrad Rzeszutek Wilk
2015-02-03 12:09 ` Formal Vote for changes to Xen Project Security Policy encoded in [PATCH v2 SECURITY-POLICY */9] (vote ends next Wed, Feb 11th) Lars Kurth
2015-02-03 12:17   ` Ian Campbell
2015-02-03 13:25   ` Jan Beulich
2015-02-03 13:35   ` Ian Jackson
2015-02-03 14:03   ` Tim Deegan
2015-02-03 14:23   ` Ian Campbell
2015-02-11 12:25   ` Lars Kurth
2015-02-27 15:45     ` Lars Kurth

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=1442924950.10338.157.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=lars.kurth.xen@gmail.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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.