From: "Giovanni Bajo" <rasky@develer.com>
To: "Daniel Berlin" <dberlin@dberlin.org>
Cc: "Gerald Pfeifer" <gerald@pfeifer.com>,
"Paolo Bonzini" <bonzini@gnu.org>, <gcc@gcc.gnu.org>
Subject: Re: toplevel bootstrap (stage 2 project)
Date: Tue, 28 Jun 2005 17:00:00 -0000 [thread overview]
Message-ID: <030001c57c02$09c54830$0db82997@bagio> (raw)
In-Reply-To: <1119965204.8059.71.camel@dyn9002219137>
Daniel Berlin <dberlin@dberlin.org> wrote:
>> Well, because Wiki is more attractive to people writing
>> documentation for several reasons (faster than writing a HTML/TeX
>> patch and submitting it for review, etc.). Maybe we should think if
>> we want to use the Wiki as our rapid documentation prototyping:
>> people could write documentation there for review, be refined by
>> others, and eventually converted to real TeX documentation.
>
> This is what i did with the decl hierarchy documentation i submitted
> as part of the decl cleanup patch.
>
> The Texinfo version took significantly longer than the wiki portion,
> but it was mainly just mechanical formatting, etc, where wiki knows what
> to do automatically or with a trivial command and Texinfo doesn't.
I believe we could conceive something to convert raw wiki text into texinfo
with our commands. It would handle the boring part of the conversion.
Giovanni Bajo
next prev parent reply other threads:[~2005-06-28 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 13:25 CFT: " Paolo Bonzini
2005-06-22 19:00 ` Giovanni Bajo
2005-06-23 7:27 ` Paolo Bonzini
2005-06-24 23:11 ` Gerald Pfeifer
2005-06-28 9:43 ` Giovanni Bajo
2005-06-28 13:27 ` Daniel Berlin
2005-06-28 17:00 ` Giovanni Bajo [this message]
2005-06-22 21:35 ` CFT: " Geoffrey Keating
[not found] ` <m364w3hei3.fsf@localhost.localdomain>
2005-07-05 9:58 ` Paolo Bonzini
2005-08-06 11:47 ` Joseph S. Myers
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='030001c57c02$09c54830$0db82997@bagio' \
--to=rasky@develer.com \
--cc=bonzini@gnu.org \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/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).