From: "Christian Bornträger" <linux-kernel@borntraeger.net>
To: "François Cami" <stilgar2k@wanadoo.fr>, "Sean Elble" <S_Elble@yahoo.com>
Cc: joeja@mindspring.com, John Alvord <jalvo@mbay.net>,
linux-kernel@vger.kernel.org
Subject: Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
Date: Tue, 13 Nov 2001 10:39:24 +0100 [thread overview]
Message-ID: <E163a2V-0002D4-00@mrvdom01.schlund.de> (raw)
In-Reply-To: <Springmail.105.1005596822.0.40719200@www.springmail.com> <015101c16bdc$e633dbe0$0a00a8c0@intranet.mp3s.com> <3BF07147.5050503@wanadoo.fr>
In-Reply-To: <3BF07147.5050503@wanadoo.fr>
> I am wondering too... Anyone got ideas on this ?
>
> I would like to avoid some specific problems... especially
> bugs that show up when compiling a certain module / feature
> of the kernel, like the loopback in 2.4.14.
Why not introduce a linux-2.4.xx-rc?
If there is no compile error or huge problem it will become linux-2.4.xx
__without__ any change after 1 day.
If there is a problem, only a patch for this problem is applied.
Just an idea
greetings
Christian
next prev parent reply other threads:[~2001-11-13 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 20:27 Re: loop back broken in 2.2.14 joeja
2001-11-12 23:36 ` Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14) Sean Elble
2001-11-13 0:37 ` François Cami
2001-11-13 0:48 ` Sean Elble
2001-11-13 1:03 ` François Cami
2001-11-13 1:35 ` Matthew D. Pitts
2001-11-13 1:44 ` François Cami
2001-11-13 2:32 ` Sean Elble
2001-11-13 9:39 ` Christian Bornträger [this message]
2001-11-14 6:31 ` Re: loop back broken in 2.2.14 Michael Peddemors
2001-11-13 1:43 Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14) victor1 torres
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=E163a2V-0002D4-00@mrvdom01.schlund.de \
--to=linux-kernel@borntraeger.net \
--cc=S_Elble@yahoo.com \
--cc=jalvo@mbay.net \
--cc=joeja@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stilgar2k@wanadoo.fr \
/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
all inboxes | Powered by JetHome®