All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: "Richard B. Tilley  \(Brad\)" <rtilley@vt.edu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Bugs and Releases Numbers
Date: Mon, 13 Jan 2003 16:07:08 +0100	[thread overview]
Message-ID: <20030113150708.GI21826@fs.tum.de> (raw)
In-Reply-To: <1042469616.28005.36.camel@oubop4.bursar.vt.edu>

On Mon, Jan 13, 2003 at 09:53:36AM -0500, Richard B. Tilley  (Brad) wrote:

> Hello,

Hi Richard,

> How are bug patches worked into the current stable release? For example,
> the ext3 file corruption bug in 2.4.20, was that patch worked into the
> kernel or will it be included in 2.4.21? I'm confused about the exact
> details of this type of thing. If the patch was worked in to 2.4.20, how
> can one tell as the release number doesn't/hasn't changed?
>...

the kernel that was released as 2.4.20 will never be changed.

The ext3 problems are fixed in the 2.4.21-pre kernels and the fixed ext3 
code will be in 2.4.21.

> Thank you,
> 
> Brad

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2003-01-13 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13 14:53 Bugs and Releases Numbers Richard B. Tilley  (Brad)
2003-01-13 15:07 ` Adrian Bunk [this message]
2003-01-13 15:17   ` Richard B. Tilley  (Brad)
2003-01-13 22:52     ` jw schultz
2003-01-14 16:37       ` Richard B. Tilley  (Brad)

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=20030113150708.GI21826@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtilley@vt.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.