From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263280AbUDPPHY (ORCPT ); Fri, 16 Apr 2004 11:07:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263281AbUDPPHY (ORCPT ); Fri, 16 Apr 2004 11:07:24 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.31.123]:9640 "EHLO atrey.karlin.mff.cuni.cz") by vger.kernel.org with ESMTP id S263280AbUDPPHW (ORCPT ); Fri, 16 Apr 2004 11:07:22 -0400 Date: Fri, 16 Apr 2004 17:00:27 +0200 From: Pavel Machek To: Andi Kleen Cc: discuss@x86-64.org, announce@x86-64.org, linux-kernel@vger.kernel.org Subject: Re: [discuss] x86-64 2.4 tree in strict maintenance mode now Message-ID: <20040416150027.GQ468@openzaurus.ucw.cz> References: <20040414174353.1dcbda16.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040414174353.1dcbda16.ak@suse.de> User-Agent: Mutt/1.3.27i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi! > I will also not add workarounds for broken hardware to 2.4 anymore unless the change > is very simple and obvious (and even then it may be not worth it) This looks even more strict than Marcelo's rules... Is it wise? -- 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms