From: Mr R A Mercer <r.a.mercer@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: loop back broken in 2.2.14
Date: Thu, 15 Nov 2001 23:38:48 +0000 [thread overview]
Message-ID: <3BF45208.1010702@blueyonder.co.uk> (raw)
Michael Peddemors wrote:
> Yes, I seriously considered the feasibility of having 2.4.14-fixed
> kernels around, but I could just imagine trying to deal with millions of
> people trying to download known good kernels on our bandwidth...
As has been mentioned before I think that the best way to avoid little
problems like this is to have a 2.4.x-rc1 kernel around for a day, if no
problems are found then that tree becomes 2.4.x if a problem is found
then is becomes 2.4.x-rc2 etc...
Cheers
Adam
next reply other threads:[~2001-11-15 23:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 23:38 Mr R A Mercer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-14 18:17 Re: Re: loop back broken in 2.2.14 joeja
2001-11-15 21:37 ` Michael Peddemors
2001-11-15 23:31 ` J.A. Magallon
2001-11-16 4:52 ` Joe
2001-11-12 17:40 joeja
2001-11-12 20:41 ` J Sloan
2001-11-11 21:27 Joe
2001-11-11 21:35 ` François Cami
2001-11-11 21:38 ` Jeff Garzik
2001-11-11 22:28 ` J Sloan
2001-11-11 22:55 ` J Sloan
2001-11-11 21:36 ` elko
2001-11-11 21:55 ` Adrian Bunk
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=3BF45208.1010702@blueyonder.co.uk \
--to=r.a.mercer@blueyonder.co.uk \
--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