From: Mike Fedyk <mfedyk@matchmail.com>
To: DevilKin <devilkin@gmx.net>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux FSCP (Frequently Submitted Compilation Problems)? (was: Re: Loop.c File !!!!)
Date: Fri, 23 Nov 2001 12:18:00 -0800 [thread overview]
Message-ID: <20011123121800.C17332@mikef-linux.matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0111202025290.6299-100000@brick> <5.1.0.14.2.20011121082413.00abadd0@pop.gmx.net>
In-Reply-To: <5.1.0.14.2.20011121082413.00abadd0@pop.gmx.net>
On Wed, Nov 21, 2001 at 08:28:58AM +0100, DevilKin wrote:
> Hi all,
>
> Just a thought. Don't shoot the messenger/idiot that thought of it.
>
> >He's doubtless referring to the deactivate_page()
> >thing that's been talked to death on this list for
> >the past 2 weeks...
> I'm getting rather annoyed with the same problem being reported/asked about
> over and over again...
>
> Is there - or would it be nice it it would be here - a list of recent
> compilation problems encountered with stock kernels (and what to do about
> it)? (see the loop.c thingy recently, and other problems with other stock
> kernels). So we could just point the people to that thing instead of having
> these 'discussions' over and over again...
>
> It could be about only the 'full' versions, or maybe the 'pre' kernels
> too...
>
> Maybe it would even be possible to add keywords to the filtering procs of
> the lkml, so that those persons would get a sort of -automatic- email on
> the subject...
>
> Just a thought...
>
I'm sorry, but the posts that are flooding the list are well deserved.
It is a great way to encourage more testing before a new "stable" kernel is
released.
I don't like it as much as anyone else, but it is a great motivator.
Don't fix it, this system is working the way it should. Most people
will just post anyway.
Mike
next prev parent reply other threads:[~2001-11-23 20:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 23:12 Loop.c File !!!! Miguel Maria Godinho de Matos
2001-11-20 20:59 ` Ryan M. McConahy
2001-11-21 1:03 ` J Sloan
2001-11-21 7:28 ` Linux FSCP (Frequently Submitted Compilation Problems)? (was: Re: Loop.c File !!!!) DevilKin
2001-11-21 8:57 ` Matt Bernstein
2001-11-21 9:10 ` Rob Turk
2001-11-21 23:18 ` Stuart Young
2001-11-22 7:07 ` Rob Turk
2001-11-23 0:03 ` Stuart Young
2001-11-23 1:03 ` Andreas Dilger
2001-11-23 1:16 ` Richard Gooch
2001-11-23 1:20 ` Arnaldo Carvalho de Melo
2001-11-23 1:45 ` Richard Gooch
2001-11-23 4:22 ` Andreas Dilger
2001-11-23 4:38 ` Richard Gooch
2001-11-23 4:40 ` Keith Owens
2001-11-23 7:10 ` Rob Turk
2001-11-23 20:18 ` Mike Fedyk [this message]
2001-11-20 23:19 ` Loop.c File !!!! Chris Wright
2001-11-26 19:58 ` Bill Davidsen
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=20011123121800.C17332@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=devilkin@gmx.net \
--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