From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
gcc@gcc.gnu.org, Michael Cieslinski <micis@gmx.de>
Subject: Re: Some notes on the Wiki (was: 4.1 news item)
Date: Sun, 10 Jul 2005 19:45:00 -0000 [thread overview]
Message-ID: <m34qb2a1jh.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <1121020011.7757.74.camel@linux.site>
Daniel Berlin <dberlin@dberlin.org> writes:
| On Sun, 2005-07-10 at 20:14 +0200, Gabriel Dos Reis wrote:
| > Daniel Berlin <dberlin@dberlin.org> writes:
| >
| > | On Sun, 2005-07-10 at 19:31 +0200, Gerald Pfeifer wrote:
| > | > I noticed that the Wiki is getting more and more of a third place where
| > | > to find documentation in addition of gcc/doc and wwwdocs, and a parallel
| > | > universe at that, with quite some duplication and inconsistencies.
| > |
| > | Have you not yet discovered that this is because people find the
| > | documentation we have to be hard to work with, and submitting patches to
| > | write in texinfo and whatnot to be a pain in the ass?
| >
| >
| > I disagree with the notion that because our current documentation is
| > imperfect, we shall move the corrected one to the Wiki page. I think
| > we've gotten too far in putting valuables bits of GCC outside our main
| > documentation repository.
|
| This happens because
| 1. People don't want to write texinfo, and continually submit patches to
| update the docs little by little (remember, people work on docs the same
| way they do on code. Most of the time, what they have written is not
| complete yet. Which is fine for the wiki, but not for our cvs docs, it
| seems), whereas this is trivial with the wiki
| 2. The docs people seem to want to write or use don't fit anywhere in
| our current scheme.
Then, let's extend that scheme (no, I exclude Wiki :-))
-- Gaby
next prev parent reply other threads:[~2005-07-10 19:45 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 21:34 4.1 news item Daniel Berlin
2005-07-08 21:40 ` Gerald Pfeifer
2005-07-09 0:34 ` Mark Mitchell
2005-07-09 1:02 ` Daniel Berlin
2005-07-09 22:17 ` Gerald Pfeifer
2005-07-09 22:40 ` Steven Bosscher
2005-07-17 1:34 ` Daniel Berlin
2005-07-18 14:30 ` Gerald Pfeifer
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 18:12 ` Daniel Berlin
2005-07-10 19:43 ` Gabriel Dos Reis
2005-07-10 20:13 ` Daniel Berlin
2005-07-10 20:37 ` Gabriel Dos Reis
2005-07-10 20:47 ` David Edelsohn
2005-07-10 23:38 ` Gabriel Dos Reis
2005-07-10 20:55 ` Gerald Pfeifer
2005-07-10 23:39 ` Gabriel Dos Reis
2005-07-10 18:15 ` Gabriel Dos Reis
2005-07-10 18:26 ` Daniel Berlin
2005-07-10 18:55 ` Joseph S. Myers
2005-07-10 19:45 ` Gabriel Dos Reis [this message]
2005-07-10 21:30 ` Steven Bosscher
2005-07-10 20:50 ` Gerald Pfeifer
2005-07-10 22:19 ` Daniel Berlin
2005-07-10 23:41 ` Gabriel Dos Reis
2005-07-11 5:35 ` Some notes on the Wiki R Hill
2005-07-11 2:53 ` Some notes on the Wiki (was: 4.1 news item) Kaveh R. Ghazi
2005-07-11 7:00 ` Some notes on the Wiki 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
2005-07-11 10:27 ` Some notes on the Wiki (was: 4.1 news item) Giovanni Bajo
2005-07-11 11:11 ` Joseph S. Myers
2005-07-11 11:18 ` Giovanni Bajo
2005-07-11 21:34 ` Gerald Pfeifer
2005-07-11 21:36 ` Steven Bosscher
2005-07-11 21:58 ` Joseph S. Myers
2005-07-11 22:07 ` Gerald Pfeifer
2005-07-11 22:21 ` Joe Buck
2005-07-11 22:51 ` Daniel Berlin
2005-07-11 22:32 ` Gabriel Dos Reis
2005-07-11 22:07 ` Gabriel Dos Reis
2005-07-11 22:13 ` Steven Bosscher
2005-07-11 22:30 ` Gabriel Dos Reis
2005-07-10 18:41 Richard Kenner
2005-07-10 21:35 ` Steven Bosscher
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=m34qb2a1jh.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=micis@gmx.de \
/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).