From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Matt Mackall <mpm@selenic.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Christoph Hellwig <hch@infradead.org>,
Willy Tarreau <willy@w.ods.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Matthew Wilcox <willy@debian.org>
Subject: Re: Linux v2.6.8 - Oops on NFSv3
Date: Sun, 15 Aug 2004 17:10:11 -0300 [thread overview]
Message-ID: <20040815201011.GG9500@logos.cnet> (raw)
In-Reply-To: <20040814172008.GD5414@waste.org>
On Sat, Aug 14, 2004 at 12:20:08PM -0500, Matt Mackall wrote:
> On Sat, Aug 14, 2004 at 04:05:56AM -0700, Linus Torvalds wrote:
> >
> >
> > On Sat, 14 Aug 2004, Christoph Hellwig wrote:
> > >
> > > Cane we make this 2.6.9 to avoid breaking all kinds of scripts expecting
> > > three-digit kernel versions?
> >
> > Well, we've been discussing the 2.6.x.y format for a while, so I see this
> > as an opportunity to actually do it... Will it break automated scripts?
> > Maybe. But on the other hand, we'll never even find out unless we try it
> > some time.
>
> We might avoid some of this (and communicate more to end users) by
> using the 2.4 -pre and -rc nomenclature, where a release is made by
> renaming an -rc kernel. As it stands, the current 2.6 "release
> candidate" naming is a lie - there's no intent to make it a final
> release.
I agree. The renaming is done by hpa's "bless-as-final" script on master.kernel.org.
next prev parent reply other threads:[~2004-08-15 22:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-14 6:05 Linux v2.6.8 Linus Torvalds
2004-08-14 10:10 ` Linux v2.6.8 - Oops on NFSv3 Willy Tarreau
2004-08-14 10:19 ` Willy Tarreau
2004-08-14 10:34 ` Jeff Garzik
2004-08-14 10:41 ` Linus Torvalds
2004-08-14 10:35 ` Willy Tarreau
2004-08-14 10:49 ` Linus Torvalds
2004-08-14 10:55 ` Christoph Hellwig
2004-08-14 11:05 ` Linus Torvalds
2004-08-14 11:18 ` Arjan van de Ven
2004-08-14 11:27 ` Jeff Garzik
2004-08-14 11:31 ` viro
2004-08-14 12:48 ` Nur Hussein
2004-08-14 20:57 ` Greg Norris
2004-08-18 20:57 ` [PATCH] scripts/patch-kernel: use EXTRAVERSION Randy.Dunlap
2004-08-22 20:40 ` Sam Ravnborg
2005-03-15 16:15 ` [BUG] " David Greaves
2005-03-15 16:25 ` Greg KH
2005-03-15 17:44 ` Greg KH
2005-03-15 17:54 ` Matt Mackall
2005-03-15 19:55 ` Sam Ravnborg
2005-03-15 18:02 ` David Greaves
2005-03-15 18:37 ` Sam Ravnborg
2005-04-12 0:07 ` [PATCH] scripts/patch-kernel: EXTRAVERSION patches are not incremental Randy.Dunlap
2004-08-17 3:13 ` Linux v2.6.8 - Oops on NFSv3 Patrick McFarland
2004-08-14 17:20 ` Matt Mackall
2004-08-15 20:10 ` Marcelo Tosatti [this message]
2004-08-16 3:37 ` Han Boetes
2004-08-16 14:06 ` Daniel Jacobowitz
2004-08-16 22:39 ` Bill Davidsen
2004-08-18 8:29 ` Robert Schwebel
2004-08-14 15:33 ` Norman Zhang
2004-08-14 10:19 ` [patch 2.6.8-rc4-mm1] via-velocity: wrong module name in Kconfig documentation Francois Romieu
2004-09-20 18:44 ` Jeff Garzik
2004-08-14 10:30 ` Linux v2.6.8 Jeff Garzik
2004-08-14 11:19 ` Stephan von Krawczynski
2004-08-14 11:38 ` Francois Romieu
2004-08-14 11:16 ` William Lee Irwin III
2004-08-16 17:56 ` Linux v2.6.8 (compile stats) John Cherry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040815201011.GG9500@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=torvalds@osdl.org \
--cc=willy@debian.org \
--cc=willy@w.ods.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox