From: Willy Tarreau <w@1wt.eu>
To: Tony Borras <tonyb@sysdev.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.35 tree abandoned/delayed?
Date: Tue, 17 Jul 2007 07:16:48 +0200 [thread overview]
Message-ID: <20070717051646.GD943@1wt.eu> (raw)
In-Reply-To: <20070716163047.55a21e6c.tonyb@sysdev.org>
Hi Tony,
On Mon, Jul 16, 2007 at 04:30:47PM -0800, Tony Borras wrote:
> I did get the current 'pre' set of 2.4.35 (circa early
> June) patches and applied to 2.4.34.5. After fixing a goto
> mislable in one of the patches (dont remember if it was one of
> the patch-2.4.34.? or patch-2.4.35.pre5), managed to build a
> vmlinuz-2.4.35 successfully.
could you please report what the problem was, in case it's not fixed
yet ?
> Just wondered whether to expect an abandonded tree, in which
> case I will fly with this 2.4.35 build or should wait for its
> eventual release.
No it's not abandonned at all !!!
The difficulty with 2.4 is to get user feedback on patches. While in 2.6,
there are hundreds or thousands of testers for every release, in 2.4,
I have to wait longer after every release in order to start collecting
problem reports, or confirmation of fixes. People using it in production
generally cannot reboot a machine in the evening just to try a patch.
Also, subsystem maintainers have less time to spend on it and are
themselves slowed down by the slow feedback process.
That's merely why I maintain a parallel 2.4.34.X stable branch. I thought
I could release one version every 6 months, but I think that this delay
will probably slightly increase after 2.4.35, we'll see.
I still have a few patches to merge, and I expect to be able to work on
them next week-end, then release -rc1, which I expect to be the only -rc
before -final (which will probably not be true as in every -rc).
Thanks,
Willy
next prev parent reply other threads:[~2007-07-17 5:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070716133025.55327074.tonyb@sysdev.org>
2007-07-17 0:30 ` Linux 2.4.35 tree abandoned/delayed? Tony Borras
2007-07-17 5:16 ` Willy Tarreau [this message]
[not found] <8HJqo-2BV-23@gated-at.bofh.it>
[not found] ` <8HJqo-2BV-21@gated-at.bofh.it>
[not found] ` <8HNDE-JM-11@gated-at.bofh.it>
2007-07-17 6:20 ` Tony Borras
2007-07-17 7:23 ` Tony Borras
2007-07-17 20:41 ` Willy Tarreau
[not found] <8HOJx-2nt-21@gated-at.bofh.it>
[not found] ` <8HOJx-2nt-23@gated-at.bofh.it>
[not found] ` <8HOJx-2nt-25@gated-at.bofh.it>
[not found] ` <8HPFA-3Pn-17@gated-at.bofh.it>
[not found] ` <8I29I-6CE-21@gated-at.bofh.it>
2007-07-19 0:03 ` Tony Borras
2007-07-19 0:10 ` Jesper Juhl
2007-07-19 0:37 ` Tony Borras
2007-07-19 4:43 ` 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=20070717051646.GD943@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=tonyb@sysdev.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