From: "François Cami" <stilgar2k@wanadoo.fr>
To: "Matthew D. Pitts" <mpitts@suite224.net>
Cc: Sean Elble <S_Elble@yahoo.com>,
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 02:44:41 +0100 [thread overview]
Message-ID: <3BF07B09.9000801@wanadoo.fr> (raw)
In-Reply-To: <Springmail.105.1005596822.0.40719200@www.springmail.com> <00c701c16bd2$e4b11800$0a00a8c0@intranet.mp3s.com> <3BF06B44.1040709@wanadoo.fr> <015101c16bdc$e633dbe0$0a00a8c0@intranet.mp3s.com> <3BF07147.5050503@wanadoo.fr> <001501c16be3$a5b16860$1df583d0@pcs586>
Matthew D. Pitts wrote:
> Umm... Linus, when are you going to open the 2.5.x development cycle? That
> is how we used to catch this kind of thing.
*eager to test 2.5* I guess that's one good idea, yes... less 'beta' in
the current 'stable' tree means that there actually is a dev tree.
And we're back at what Sean Elble wrote about SGI having two
trees for IRIX.
François
> Matthew D. Pitts
> Pitts Computer Services
> mpitts@suite224.net
> ----- Original Message -----
> From: "François Cami" <stilgar2k@wanadoo.fr>
> To: "Sean Elble" <S_Elble@yahoo.com>
> Cc: <joeja@mindspring.com>; "John Alvord" <jalvo@mbay.net>;
> <linux-kernel@vger.kernel.org>
> Sent: Monday, November 12, 2001 8:03 PM
> Subject: Re: Testing Kernel Releases Before Being Released (Was Re: Re: loop
> back broken in 2.2.14)
>
>
>
>>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.
>>
>>Those should be very easy to get rid of
>>[it only takes some kernel testers to debug that early, if only
>>there actually were a feature freeze that last for one day...].
>>
>>François
>>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2001-11-13 1:42 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 [this message]
2001-11-13 2:32 ` Sean Elble
2001-11-13 9:39 ` Christian Bornträger
2001-11-14 6:31 ` Re: loop back broken in 2.2.14 Michael Peddemors
-- strict thread matches above, loose matches on Subject: below --
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=3BF07B09.9000801@wanadoo.fr \
--to=stilgar2k@wanadoo.fr \
--cc=S_Elble@yahoo.com \
--cc=jalvo@mbay.net \
--cc=joeja@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpitts@suite224.net \
/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