From: "Ian E. Morgan" <imorgan@webcon.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Reconsider dropping "-final" EXTRAVERSION from 2.6.9 release
Date: Sat, 16 Oct 2004 13:33:21 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0410161316500.5062@dark.webcon.ca> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 834 bytes --]
I hope other people with influence will speak up on this matter.
I seems like each new kernel in recent times is introducing new release
methodology (the whole "2.6.8.1" fiasco is still fresh in all our minds). Is
the "-final" EXTRAVERSION really necessary?
Thankfully, 2.6.9-final is still in the testing tree. It is my hopes that it
will actually be released as "2.6.9". That's always been good enough.
Linus says "Let's try the 2.4.x release methodology." The "2.4.x release
methodology" was to change a "Foo-rcX" to a final "Foo" release with no
changes. I see no evidence that any 2.4 kernel (or _any_ Linux kernel) was
ever released as "Foo-final". It may be OK to _call_ it a "final" version
when referring to it, but adding "-final" to the EXTRAVERSION field is just
aggravating and redundant.
My 2¢.
Regards,
Ian Morgan
next reply other threads:[~2004-10-16 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 17:33 Ian E. Morgan [this message]
2004-10-16 22:00 ` Alan Cox
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=Pine.LNX.4.61.0410161316500.5062@dark.webcon.ca \
--to=imorgan@webcon.ca \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®