From: joeja@mindspring.com
To: linux-kernel@borntraeger.net
Cc: stilgar2k@wanadoo.fr, Sean Elble <S_Elble@yahoo.com>,
John Alvord <jalvo@mbay.net>,
linux-kernel@vger.kernel.org
Subject: Re: Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop back broken in 2.2.14)
Date: Tue, 13 Nov 2001 12:30:18 -0500 [thread overview]
Message-ID: <Springmail.105.1005672618.0.57892500@www.springmail.com> (raw)
The real solution I think is for Linus to open up 2.5.
If I remember correclty by the time that 2.2 was at 14, 2.3 was open.
Joe
Christian =?iso-8859-15?q?Borntr=E4ger?= <linux-kernel@borntraeger.net> wrote:
> > 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
reply other threads:[~2001-11-13 17:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Springmail.105.1005672618.0.57892500@www.springmail.com \
--to=joeja@mindspring.com \
--cc=S_Elble@yahoo.com \
--cc=jalvo@mbay.net \
--cc=linux-kernel@borntraeger.net \
--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