Re: The naming wars continue...

From: Matt Mackall (mpm_at_selenic.com)
Date: 10/23/04

Next message: Greg KH: "Re: [PATCH] PCI fixes for 2.6.9"

Previous message: Phil Oester: "Re: [PATCH] Update to Documentation/ramdisk.txt"
In reply to: Linus Torvalds: "The naming wars continue..."
Next in thread: Con Kolivas: "Re: The naming wars continue..."
Reply: Con Kolivas: "Re: The naming wars continue..."
Reply: William Lee Irwin III: "Re: The naming wars continue..."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date:	Fri, 22 Oct 2004 18:46:31 -0500
To: Linus Torvalds <torvalds@osdl.org>

On Fri, Oct 22, 2004 at 03:05:13PM -0700, Linus Torvalds wrote:
> And the fact is, I can't see the point. I'll just call it all "-rcX",
> because I (very obviously) have no clue where the cut-over-point from
> "pre" to "rc" is, or (even more painfully obviously) where it will become
> the final next release.

This should be easy: the cut-over should be when you're tempted to
rename it 2.6.next. If you have no intention (or hope) of renaming
2.6.x-rc1 to 2.6.x, it is not a "release candidate" by definition.

What's the point? It serves as a signal that a) we're not accepting
more big changes b) we think it's ready for primetime and needs
serious QA c) when 2.6.next gets released, the _exact code_ has gone
through a test cycle and we can have some confidence that there won't
be any nasty 0-day bugs when we go to install 2.6.next on a production
machine.

> (*) In other words, I had a beer and watched TV. Mmm... Donuts.

Please devote some more beer and TV to this problem after you release
2.6.10.

-- 
Mathematics is the supreme nostalgia of our time.
-
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/

Next message: Greg KH: "Re: [PATCH] PCI fixes for 2.6.9"

Previous message: Phil Oester: "Re: [PATCH] Update to Documentation/ramdisk.txt"
In reply to: Linus Torvalds: "The naming wars continue..."
Next in thread: Con Kolivas: "Re: The naming wars continue..."
Reply: Con Kolivas: "Re: The naming wars continue..."
Reply: William Lee Irwin III: "Re: The naming wars continue..."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Relevant Pages

Re: 2.6.5-rc2-aa1
... > b*tkeeper will automagically notice the rename when Linus merges ... to move rmap.c to objrmap.c and Linus pulls from your ... bitkeeper tree. ... 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/ ...
(Linux-Kernel)
Re: dont let mmap allocate down to zero
... >> AFAICS it is covered. ... > is very intentional to deny the MREMAP_FIXED to 0 case of mremap. ... > It was also the intention to deny the MAP_FIXED to 0 case of mmap, ... send the line "unsubscribe linux-kernel" in ...
(Linux-Kernel)
Re: Re: more git updates..
... > Rename should just work. ... It will create a new tree object and you ... > will notice that in the entry that changed, the hash for the blob ... send the line "unsubscribe linux-kernel" in ...
(Linux-Kernel)
Re: seq_file API strangeness
... boom. ... resulting in an unconditional unlock of my lock. ... > Was this by intention? ... send the line "unsubscribe linux-kernel" in ...
(Linux-Kernel)
Re: Sabotaged PaXtest (was: Re: Patch 4/6 randomize the stack pointer)
... > it still ran with an executable stack, that was not the intention but ... > rather an oversight, it'll be fixed in the next release. ... send the line "unsubscribe linux-kernel" in ...
(Linux-Kernel)