From: Enrico Demarin <enricod@videotron.ca>
To: Alain Fauconnet <alain@ait.ac.th>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Ibm Serveraid Problem with 2.4.25
Date: Mon, 01 Mar 2004 10:01:13 -0500 [thread overview]
Message-ID: <1078153079.4447.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20040301033017.GD1270@ait.ac.th>
Alain , I am pasting you an email i got from Marcelo Tosatti, which I
think clarifies pretty well the history of 2.4.24 and 2.4.25 :
-- snip --
2.4.24 was under development (had -pre1, -pre2 and -pre3 released).
At that point, we had to release 2.4.24 without the "-pre" changes (only
with the security fixes).
So basically 2.4.24-pre was renamed to 2.4.25-pre, and 2.4.25-pre4 was
released.
-- snip --
- Enrico
On Sun, 2004-02-29 at 22:30, Alain Fauconnet wrote:
> Enrico,
>
> Thanks for the update, but...
>
> On Sun, Feb 29, 2004 at 10:10:30PM -0500, Enrico Demarin wrote:
> > Alain,
> >
> > so far Jo went through all the pre2.4.24 and 25 and the bug appeared
> > in 2.4.24pre1.
>
> Are you meaning that the bug was already present in the 2.4.24
> release? I'm a bit confused here.
next prev parent reply other threads:[~2004-03-01 14:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 9:12 Ibm Serveraid Problem with 2.4.25 Jo Christian Buvarp
2004-02-26 23:48 ` Enrico Demarin
2004-02-27 1:48 ` Enrico Demarin
2004-02-27 3:14 ` Marcelo Tosatti
2004-02-27 2:37 ` Enrico Demarin
2004-02-27 7:16 ` Jo Christian Buvarp
2004-02-27 14:36 ` Marcelo Tosatti
2004-03-01 2:10 ` Alain Fauconnet
2004-03-01 3:10 ` Enrico Demarin
2004-03-01 3:30 ` Alain Fauconnet
2004-03-01 15:01 ` Enrico Demarin [this message]
2004-03-01 15:51 ` Marcelo Tosatti
2004-03-01 17:24 ` Chuck Lever
2004-03-01 18:23 ` Marcelo Tosatti
2004-03-01 18:39 ` Chuck Lever
2004-03-01 18:41 ` Enrico Demarin
2004-03-02 5:18 ` Chuck Lever
[not found] <Pine.LNX.4.44.0403011149560.4148-200000@dmt.cyclades>
2004-03-01 15:38 ` Jo Christian Buvarp
-- strict thread matches above, loose matches on Subject: below --
2004-03-01 21:38 Alan Swanson
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=1078153079.4447.2.camel@localhost.localdomain \
--to=enricod@videotron.ca \
--cc=alain@ait.ac.th \
--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 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.