From: Willy Tarreau <w@1wt.eu>
To: Grant Coady <gcoady.lk@gmail.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
linux-kernel@vger.kernel.org, mtosatti@redhat.com,
alan@lxorguk.ukuu.org.uk
Subject: Re: Linux v2.4.33-rc3 (and a new v2.4 maintainer)
Date: Fri, 28 Jul 2006 06:55:07 +0200 [thread overview]
Message-ID: <20060728045507.GC17478@1wt.eu> (raw)
In-Reply-To: <nbuic2ljd8n5g43k74tussq2hm5nvrn04e@4ax.com>
On Fri, Jul 28, 2006 at 12:46:31PM +1000, Grant Coady wrote:
> On Fri, 28 Jul 2006 04:16:42 +0200 (MEST), Mikael Pettersson <mikpe@it.uu.se> wrote:
>
> >On Thu, 27 Jul 2006 18:30:19 -0300, Marcelo Tosatti wrote:
> >>Here goes the third (and hopefully last) release candidate of v2.4.33.
> >
> >http://www.kernel.org/pub/linux/kernel/v2.4/testing/patch-2.4.33-rc3.bz2
> >is only 854 bytes long, and once bunzip2:ed it looks like it's the
> >incremental diff between rc2 and rc3. Usually the full pre/rc patches
> >go in testing/ with the incrementals going into testing/incr/.
> >
> >No big deal, but it would feel better with a proper -rc3 patch there.
> >
>
> Yeah, stuff happens ;)
I will let Marcelo fix it.
> At the moment one needs 2.4.32 plus patches -rc2 and -rc3, like you
> say, very obvious from patch file sizes ;)
>
> At least -rc3 goes okay on 7 of 7 test boxen here:
> <http://bugsplatter.mine.nu/test/linux-2.4/>
Fine, thanks for the test, Grant. I expect to release hf32.7 soon, all
the patches are already waiting in the git tree. But I won't announce
a date anymore, everytime I did so I did not respect it at all.
> Cheers,
> Grant.
Cheers,
Willy
next prev parent reply other threads:[~2006-07-28 4:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 2:16 Linux v2.4.33-rc3 (and a new v2.4 maintainer) Mikael Pettersson
2006-07-28 2:46 ` Grant Coady
2006-07-28 4:55 ` Willy Tarreau [this message]
2006-07-28 23:24 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2006-07-27 21:30 Marcelo Tosatti
2006-07-28 1:11 ` Bill Davidsen
2006-07-28 4:49 ` Willy Tarreau
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=20060728045507.GC17478@1wt.eu \
--to=w@1wt.eu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gcoady.lk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mtosatti@redhat.com \
/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