Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751469AbWIYSzZ (ORCPT ); Mon, 25 Sep 2006 14:55:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751474AbWIYSzZ (ORCPT ); Mon, 25 Sep 2006 14:55:25 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:6610 "EHLO ogre.sisk.pl") by vger.kernel.org with ESMTP id S1751469AbWIYSzY (ORCPT ); Mon, 25 Sep 2006 14:55:24 -0400 From: "Rafael J. Wysocki" To: Ingo Molnar Subject: Re: 2.6.19 -mm merge plans Date: Mon, 25 Sep 2006 20:57:56 +0200 User-Agent: KMail/1.9.1 Cc: Nick Piggin , Linus Torvalds , Andrew Morton , Alan Cox , Jeff Garzik , Linux Kernel Mailing List References: <20060920135438.d7dd362b.akpm@osdl.org> <451747EE.50900@yahoo.com.au> <20060925115352.GA15705@elte.hu> In-Reply-To: <20060925115352.GA15705@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609252057.57149.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1022 Lines: 29 On Monday, 25 September 2006 13:53, Ingo Molnar wrote: > > * Nick Piggin wrote: > > > OTOH, if we were worried about confusing people, we wouldn't be using > > the acronym 'rc' for our 'Ridiculous Count', and have our rc1 denote > > the result of 2 weeks of stuffing the tree with new features and > > intrusive changes, where people might mistake that for the much more > > common RC-as-in-'Release Candidate'. :) Well, "release" need not mean anything really stable. Let's think of it as certain state of the tree that has been given a label for future reference. > oh, we could call the first one -rc0 then :-) Good idea, IMHO. :-) Greetings, Rafael -- You never change things by fighting the existing reality. R. Buckminster Fuller - 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/