public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Andersen <anddan@linux-user.net>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] README (resend) - Explain new 2.6.xx.x version number
Date: Wed, 15 Sep 2004 00:23:42 +0200	[thread overview]
Message-ID: <41476F6E.8030205@linux-user.net> (raw)
In-Reply-To: <20040914214356.GG13788@redhat.com>

Dave Jones wrote:
> On Tue, Sep 14, 2004 at 11:35:15PM +0200, Daniel Andersen wrote:
> 
>  > +   In case of a
>  > +   bug-fix release such as if eg. 2.6.8.2 is released after 2.6.9 has
>  > +   been released, 2.6.9 is still to be considered the newest kernel
>  > +   release of all current kernels.
> 
> This bit seems odd to me. Why would a 2.6.8.2 get released, when there's
> a newer 2.6.9 which should fix whatever was relevant to get into 2.6.8.x ?
> 
> 		Dave
> 

This was discussed in the thread "Linux 2.6.9-rc1". Linus said there was 
a remote possibility it could happen some day so I thought it was a good 
thing to mention.

Daniel Andersen

--

  reply	other threads:[~2004-09-14 22:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 21:35 [PATCH] README (resend) - Explain new 2.6.xx.x version number Daniel Andersen
2004-09-14 21:43 ` Dave Jones
2004-09-14 22:23   ` Daniel Andersen [this message]
2004-09-15  1:02 ` Roman Zippel
2004-09-15  2:25   ` Daniel Andersen
2004-09-15  2:40   ` Randy.Dunlap
2004-09-15  8:01     ` Denis Vlasenko
2004-09-15 11:06     ` Roman Zippel
2004-09-15 15:25       ` Randy.Dunlap
2004-09-15 15:57         ` Roman Zippel

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=41476F6E.8030205@linux-user.net \
    --to=anddan@linux-user.net \
    --cc=davej@redhat.com \
    --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