From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: removal of ia64 port Date: Thu, 22 Mar 2012 11:19:13 +0000 Message-ID: References: <4F6B1536020000780007A326@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F6B1536020000780007A326@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , KUWAMURA Shin'ya Cc: Ian Campbell , xen-ia64-devel , Lars Kurth , xen-devel List-Id: xen-devel@lists.xenproject.org On 22/03/2012 11:04, "Jan Beulich" wrote: >>>> On 22.03.12 at 11:58, Keir Fraser wrote: >> On 21/03/2012 08:45, "Jan Beulich" 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. > > Then how about waiting a few more days for eventual feedback from > the supposed maintainer or the ia64 list, but remove it the latest right > before -rc1? Cc Ian Campbell, who is managing the release process. Also Lars, who may have an opinion on protocol for removing a port. However, as far as my own vote counts these days, I agree and see no reason for a long-unmaintained port to hang around during the 4.2 release process. -- Keir > Jan >