From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@suse.com>,
KUWAMURA Shin'ya <kuwa@jp.fujitsu.com>,
xen-devel <xen-devel@lists.xen.org>
Cc: xen-ia64-devel <xen-ia64-devel@lists.xen.org>
Subject: Re: removal of ia64 port
Date: Thu, 22 Mar 2012 10:58:25 +0000 [thread overview]
Message-ID: <CB90B651.3C22C%keir@xen.org> (raw)
In-Reply-To: <4F69A3340200007800079D1B@nat28.tlf.novell.com>
On 21/03/2012 08:45, "Jan Beulich" <JBeulich@suse.com> wrote:
> Given that the ia64 port hasn't really been maintained for the last couple
> of years (I am apparently the only one to try to keep it building at least,
> but I suspect that it has been non-functional for quite a while), I'd like to
> propose to remove the port. After quite some time of trying to get an
> opinion from Intel on this, I was now notified of their agreement to this
> move.
>
> From my pov, the only thing to discuss here is whether this should
> happen right away, or after 4.2 went out (then with a formal removal
> proposal in that release - the port's state isn't being reflected correctly
> anyway in ./MAINTAINERS afaict).
>
> Thoughts?
I don't think it would be unreasonable to remove it ahead of 4.2. It's not
been working for a long time now.
-- Keir
> Thanks, Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-03-22 10:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 8:45 removal of ia64 port Jan Beulich
2012-03-22 10:58 ` Keir Fraser [this message]
2012-03-22 11:04 ` Jan Beulich
2012-03-22 11:19 ` Keir Fraser
2012-03-22 12:10 ` Ian Campbell
2012-03-23 6:52 ` KUWAMURA Shin'ya
[not found] ` <20120323.155249.425911897.kuwa@jp.fujitsu.com>
2012-03-23 9:01 ` Jan Beulich
2012-03-29 9:13 ` Ian Campbell
2012-03-30 8:54 ` KUWAMURA Shin'ya
[not found] ` <20120330.175445.321377065.kuwa@jp.fujitsu.com>
2012-04-02 15:16 ` Jan Beulich
2012-04-02 15:33 ` Keir Fraser
2012-04-03 8:18 ` Jan Beulich
2012-04-03 8:57 ` Keir Fraser
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=CB90B651.3C22C%keir@xen.org \
--to=keir@xen.org \
--cc=JBeulich@suse.com \
--cc=kuwa@jp.fujitsu.com \
--cc=xen-devel@lists.xen.org \
--cc=xen-ia64-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 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).