Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261369AbVACAtf (ORCPT ); Sun, 2 Jan 2005 19:49:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261366AbVACAte (ORCPT ); Sun, 2 Jan 2005 19:49:34 -0500 Received: from wproxy.gmail.com ([64.233.184.202]:12767 "EHLO wproxy.gmail.com") by vger.kernel.org with ESMTP id S261174AbVACAta (ORCPT ); Sun, 2 Jan 2005 19:49:30 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=UaLebdxo346FjYY/u7AeGpvOx/QiHhu3/GAN6Y43uk1ZNy8tvapIUy1dzLqea5vQZT5ZL7YssOutOWbT88ADBurvNRDYoiZ5HqjdRkdCK4pGpGpKwbWLS0ZJ7rbVUDidMh+mZlBRRj/EtxlPvUNSZj5Vdm4/RIzMzDlIUc7PeHU= Message-ID: <799406d60501021649737f1bd@mail.gmail.com> Date: Mon, 3 Jan 2005 00:49:22 +0000 From: Adam Mercer Reply-To: Adam Mercer To: linux-kernel@vger.kernel.org Subject: Re: starting with 2.7 In-Reply-To: <20050103003857.GJ4183@stusta.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <1697129508.20050102210332@dns.toxicfilms.tv> <20050102203615.GL29332@holomorphy.com> <20050102212427.GG2818@pclin040.win.tue.nl> <20050102214211.GM29332@holomorphy.com> <20050102221534.GG4183@stusta.de> <20050103001917.GO29332@holomorphy.com> <20050103003857.GJ4183@stusta.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 573 Lines: 18 On Mon, 3 Jan 2005 01:38:58 +0100, Adrian Bunk wrote: > 2.4.27 -> 2.4.28 is a kernel upgrade that is very unlikely to cause > problems. > > Compared to this, 2.6.9 -> 2.6.10 is much more likely to break an > existing setup that worked in 2.6.9 . IIRC 2.4.9 -> 2.4.10 broke a few setups as well. Cheers Adam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/