From: John Bradford <john@grabjohn.com>
To: Bill Davidsen <davidsen@tmr.com>,
Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.0-test9
Date: Thu, 30 Oct 2003 17:23:38 GMT [thread overview]
Message-ID: <200310301723.h9UHNcl2000254@81-2-122-30.bradfords.org.uk> (raw)
In-Reply-To: <Pine.LNX.3.96.1031030113206.6313A-100000@gatekeeper.tmr.com>
> > > If the idea is to tell people to read the post-Halowe'en doc and a year
> > > of LKML, it is much the same as telling people to wait for a
> > > distribution.
> >
> > Isn't the purpose of the post-haloween doc to tell people what
> > changed and what needed to be upgraded? What about the
> > linux/Documentation/Changes file?
>
> Given that it is a year out of date and general in nature, it's still a
> pretty useful docuement to someone who does a lot of fiddling anyway.
> But what I think would be very useful would be a small (one screen?)
> HTML doc with links to versions which are current today, one page each
> for a few major distros covering tweaks to startup file and the like,
> and a page of things which aren't mentioned in the post Halowe'en doc,
> like the things that aren't available in modules anymore.
Or a filter which takes a 2.4 .config file as input, and outputs the
relevant sections of the post-Haloween document based on that :-).
John.
next prev parent reply other threads:[~2003-10-30 17:21 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 1:16 Linux 2.6.0-test9 Andries.Brouwer
2003-10-26 3:12 ` OGAWA Hirofumi
2003-10-26 5:48 ` Linus Torvalds
2003-10-27 23:26 ` bill davidsen
2003-10-30 9:20 ` Russell King
2003-10-30 16:44 ` Bill Davidsen
2003-10-30 17:23 ` John Bradford [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-27 10:58 Andries.Brouwer
2003-10-27 9:47 Mikael Pettersson
2003-10-27 1:48 Andries.Brouwer
2003-10-27 2:10 ` Linus Torvalds
2003-10-27 9:40 ` David S. Miller
2003-10-26 19:40 Andries.Brouwer
2003-10-27 0:01 ` Andrew Morton
2003-10-27 0:21 ` Linus Torvalds
2003-10-27 0:28 ` Linus Torvalds
2003-10-27 6:43 ` David S. Miller
2003-10-27 19:54 ` kuznet
2003-10-27 19:36 ` kuznet
2003-10-28 0:42 ` Tommy Christensen
2003-10-28 18:25 ` kuznet
2003-10-26 18:51 P. Christeas
2003-10-27 3:16 ` Andrew Morton
2003-10-26 15:32 Shane Shrybman
2003-10-26 16:27 ` Marco Roeland
2003-10-26 11:08 Andries.Brouwer
2003-10-26 13:57 ` OGAWA Hirofumi
2003-10-26 10:59 Andries.Brouwer
2003-10-27 23:37 ` bill davidsen
2003-10-26 10:26 Andries.Brouwer
2003-10-25 19:09 Linus Torvalds
2003-10-25 19:52 ` Marcelo Tosatti
2003-10-25 20:14 ` viro
2003-10-25 22:35 ` Linus Torvalds
2003-10-25 23:45 ` Jose Luis Domingo Lopez
2003-10-26 12:05 ` Patrik Wallstrom
2003-10-27 18:21 ` Patrik Wallstrom
2003-10-27 22:51 ` bill davidsen
2003-10-28 2:12 ` Jeff Garzik
2003-10-28 4:52 ` 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=200310301723.h9UHNcl2000254@81-2-122-30.bradfords.org.uk \
--to=john@grabjohn.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).