Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756059AbZJFCwd (ORCPT ); Mon, 5 Oct 2009 22:52:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754766AbZJFCwc (ORCPT ); Mon, 5 Oct 2009 22:52:32 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:44224 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754104AbZJFCwc (ORCPT ); Mon, 5 Oct 2009 22:52:32 -0400 Subject: Re: Linux 2.6.32-rc3 From: Dirk Hohndel To: Len Brown Cc: Linus Torvalds , Linux Kernel Mailing List In-Reply-To: References: Content-Type: text/plain Organization: Intel Open Source Technology Center Date: Mon, 05 Oct 2009 19:51:42 -0700 Message-Id: <1254797502.14122.146.camel@dhohndel-mobl.amr.corp.intel.com> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1553 Lines: 38 On Mon, 2009-10-05 at 21:57 -0400, Len Brown wrote: > > do you mean -rc2 as in the Makefile (ie really -rc1) or -rc2 as in the > > tagged release. > > We have a similar problem with the period between, say, 2.6.X and > 2.6.Y-rc1. The Makefile still says 2.6.X, yet during the 2.6.Y > merge window the tree is very different from 2.6.X. > > This confuses things like my scripts that take a source tree tarball, > and (re)generate config files for build testing based on the tags > in the Makefile. There is no way for the scripts to know the > post 2.6.X tree not the same as 2.6.X itself, the new configs > overwrite the old, overwrite the old results etc. > > I think that BenH also had troubles with this issue and pointed > it out a while back, but you were not convinced at the time that > it was a problem worth solving. > > This could be clarified if you update Makefile on the 1st commit > after 2.6.X is frozen to simply be 2.6.Y-merge or 2.6.Y-rc0 > or something. Anything but 2.6.X. I have seen this request many times and it seems to make perfect sense. The first commit applied after a release should change the version number to "something" - and "2.6.next-rc0" sounds as good as anything else that has been proposed so far. /D -- Dirk Hohndel Intel Open Source Technology Center -- 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/