From: "Robert Thorpe" <rthorpe@realworldtech.com>
To: <gcc@gcc.gnu.org>
Subject: Re: Some notes on the Wiki
Date: Mon, 11 Jul 2005 20:10:00 -0000 [thread overview]
Message-ID: <0eca48d3d0944725845e0a180be69259@realworldtech.com> (raw)
> I believe the Wiki is an invaluable documentation tool, precisely
> because it allows such an unencumbered contribution process.
>
> I agree. I wasn't suggesting that the Wiki has no value, but rather
> that it's not a substitute for the more formal documentation. Were it
> not for copyright issues, one could view the Wiki as an ongoing draft
> process for the documentation.
A comment from a user...
Please, please, please don't move GCC internals documentation to a Wiki.
Even to users the internals documentation is useful. It's useful when trying to find out why GCC is doing the things it does with the code given to it, it indicates where to look to find things in the source. This would be much harder if it were a wiki, in particular finding information on the version of GCC you're using would be much more difficult.
Also, a web-browser is much slower than an info-browser, especially when doing searchs.
next reply other threads:[~2005-07-11 20:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 20:10 Robert Thorpe [this message]
2005-07-11 20:28 ` Daniel Berlin
2005-07-11 20:48 ` Gabriel Dos Reis
2005-07-11 21:05 ` Daniel Berlin
2005-07-12 20:37 ` Alexandre Oliva
2005-07-11 21:02 ` Nicholas Nethercote
2005-07-11 21:13 ` Daniel Berlin
2005-07-11 21:23 ` Andreas Schwab
2005-07-11 22:10 ` Daniel Berlin
2005-07-11 22:59 ` Andreas Schwab
2005-07-11 22:08 ` Gabriel Dos Reis
2005-07-11 22:38 ` chris jefferson
2005-07-11 22:47 ` Daniel Berlin
2005-07-12 0:36 ` Kurt Wall
2005-07-12 8:48 ` Bernd Schmidt
-- strict thread matches above, loose matches on Subject: below --
2005-07-12 9:24 Robert Thorpe
2005-07-11 16:10 Richard Kenner
2005-07-11 15:03 Haren Visavadia
[not found] <28206.1121071576@www23.gmx.net>
2005-07-11 8:50 ` Michael Cieslinski
2005-07-11 11:21 ` Joseph S. Myers
2005-07-11 11:58 ` Russell Shaw
2005-07-11 13:54 ` Paul Koning
2005-07-11 14:11 ` Steven Bosscher
2005-07-11 14:19 ` Diego Novillo
2005-07-11 14:22 ` Steven Bosscher
2005-07-11 14:51 ` Bernd Schmidt
2005-07-11 14:54 ` Steven Bosscher
2005-07-11 15:19 ` Joseph S. Myers
2005-07-11 15:31 ` Daniel Berlin
2005-07-11 15:21 ` Andrew Haley
2005-07-11 15:30 ` Steven Bosscher
2005-07-11 15:31 ` Steven Bosscher
2005-07-11 17:20 ` Mike Stump
2005-07-11 15:23 ` Daniel Berlin
2005-07-11 14:41 ` Haren Visavadia
2005-07-11 14:50 ` Diego Novillo
2005-07-15 17:20 ` Gerald Pfeifer
2005-07-11 20:43 ` Kevin Handy
2005-07-11 20:54 ` Paul Koning
2005-07-08 21:34 4.1 news item Daniel Berlin
2005-07-08 21:40 ` Gerald Pfeifer
2005-07-09 1:02 ` Daniel Berlin
2005-07-10 17:31 ` Some notes on the Wiki (was: 4.1 news item) Gerald Pfeifer
2005-07-10 17:53 ` Daniel Berlin
2005-07-10 20:50 ` Gerald Pfeifer
2005-07-11 5:35 ` Some notes on the Wiki R Hill
2005-07-11 7:00 ` Paolo Bonzini
2005-07-10 21:40 ` Some notes on the Wiki (was: 4.1 news item) Andrew Pinski
2005-07-10 21:50 ` Gerald Pfeifer
2005-07-11 7:03 ` Some notes on the Wiki Paolo Bonzini
2005-07-11 21:32 ` Gerald Pfeifer
2005-07-11 7:10 ` Paolo Bonzini
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=0eca48d3d0944725845e0a180be69259@realworldtech.com \
--to=rthorpe@realworldtech.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).