From: "Skip Tavakkolian" <fst@centurytel.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9.ps (was:Hi together | a few newbie questions)
Date: Tue, 17 Dec 2002 15:12:14 -0800 [thread overview]
Message-ID: <a7cb57cd6a1c0acbb59d49f7451e7601@centurytel.net> (raw)
> The advantages of the wiki format would be:
> * easy updating by anyone who can examine a particular bit of kernel code
> * up-to-date version is always the one read (especially if the chapters
> are seperately downloadable - those of us on dial-up connections might not
> want to download the entire 1500K for an updated version that fixes a
> spelling error, but smaller sections would be manegable)
My recent experience with the Wiki pages tells me that the
"Kernel Notes" shouldn't be trusted to wiki and group editing.
There are very few people on this list that could reasonably do
the updates that it seems Wiki-fying is counterproductive.
There is plenty of raw information (including the kernel source).
What saves everyone time is knowing that a trusted authority has
written the commentary with a coherent classification of functions.
next reply other threads:[~2002-12-17 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-17 23:12 Skip Tavakkolian [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-17 21:50 Joel Salomon
2002-12-17 8:57 Fco.J.Ballesteros
2002-12-16 22:05 Joel Salomon
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=a7cb57cd6a1c0acbb59d49f7451e7601@centurytel.net \
--to=fst@centurytel.net \
--cc=9fans@cse.psu.edu \
/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).