From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: KUWAMURA Shin'ya <kuwa@jp.fujitsu.com>,
xen-ia64-devel@lists.xen.org, Ian.Campbell@citrix.com,
xen-devel@lists.xen.org
Subject: Re: removal of ia64 port
Date: Mon, 02 Apr 2012 16:33:34 +0100 [thread overview]
Message-ID: <CB9F855E.2FDCE%keir.xen@gmail.com> (raw)
In-Reply-To: <4F79DEEB020000780007C0F3@nat28.tlf.novell.com>
On 02/04/2012 16:16, "Jan Beulich" <JBeulich@suse.com> wrote:
>>>> On 30.03.12 at 10:54, "KUWAMURA Shin'ya" <kuwa@jp.fujitsu.com> wrote:
>>>>>>> On Thu, 29 Mar 2012 10:13:04 +0100
>>>>>>> Ian.Campbell@citrix.com(Ian Campbell) said:
>>>
>>> Kuwamura, what is your motivation for wanting to keeping the ia64 port
>>> in 4.2 and beyond?
>>
>> As the result of my consideration,
>> I agree that ia64 port will be dropped on xen-unstable, since it seems
>> to be hardly needed:
>> - There was little discussion on xen-ia64-devel ML recently.
>> - There are few Xen ia64 developers.
>> - No new feature will be added.
>
> Keir,
>
> now that we apparently having reached consensus here, are you
> going to purge the ia64 bits from the tree, or do you want me to?
Please go ahead.
-- Keir
> Jan
>
next prev parent reply other threads:[~2012-04-02 15:33 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
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 [this message]
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=CB9F855E.2FDCE%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Campbell@citrix.com \
--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 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.