From: Stuart Young <sgy@amc.com.au>
To: "Rob Turk" <r.turk@chello.nl>, linux-kernel@vger.kernel.org
Subject: Re: Linux FSCP (Frequently Submitted Compilation Problems)? (was: Re: Loop.c File !!!!)
Date: Thu, 22 Nov 2001 10:18:13 +1100 [thread overview]
Message-ID: <5.1.0.14.0.20011122100929.009ead30@mail.amc.localnet> (raw)
In-Reply-To: <9tfr1k$a5l$1@ncc1701.cistron.net>
In-Reply-To: <Pine.LNX.4.21.0111202025290.6299-100000@brick> <5.1.0.14.2.20011121082413.00abadd0@pop.gmx.net>
At 10:10 AM 21/11/01 +0100, Rob Turk wrote:
>Good suggestion. Unfortunately, many people obviously do not take the time
>to read the newsgroup before they post, so what do you propose will be the
>mechanism to encourage them to lookup existing issues?
Why not do it like the current Changelog, put it in the kernel repository,
and make sure it hits all the mirrors. A little selective advertising (eg:
someone mention it on slashdot, newsforge, debianplanet, etc), and people
will start using it. Just suffix the file with the version number, just
like the Changelog. Because the file will be small, it's possible that some
mirrors will get quick updates before they get the kernel itself. This
covers all the version specific problems at least.
Stuart Young - sgy@amc.com.au
(aka Cefiar) - cefiar1@optushome.com.au
[All opinions expressed in the above message are my]
[own and not necessarily the views of my employer..]
next prev parent reply other threads:[~2001-11-21 23: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 [this message]
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:40 ` Keith Owens
2001-11-23 4:38 ` Richard Gooch
2001-11-23 7:10 ` Rob Turk
2001-11-23 20:18 ` Mike Fedyk
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=5.1.0.14.0.20011122100929.009ead30@mail.amc.localnet \
--to=sgy@amc.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=r.turk@chello.nl \
/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®