From: Ian Lance Taylor <iant@google.com>
To: Diego Novillo <dnovillo@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [tuples] API documentation
Date: Thu, 12 Jun 2008 19:54:00 -0000 [thread overview]
Message-ID: <m3skviqvny.fsf@google.com> (raw)
In-Reply-To: <b798aad50806121147o67c4979fi79e793c15fa3a8e5@mail.gmail.com> (Diego Novillo's message of "Thu\, 12 Jun 2008 14\:47\:12 -0400")
Diego Novillo <dnovillo@google.com> writes:
> I just finished going through the API document adding missing content
> and updating stale information. While there are various aspects of
> GIMPLE that are not covered in the document, it is probably complete
> enough for converting/adding gimple code.
>
> At the moment I'm wondering what would be the best way to host this
> documentation. Do we leave it on some web-based form (wiki or google
> docs)? Do we move it to the source tree as .texi files?
>
> I can see advantages to both approaches. Leaving it on the web, makes
> it easier to edit and evolve. Moving to the source tree makes it
> easier to version but harder to edit.
I think that when it is reasonably stable it should move into a .texi
file in the source code. That is there the gcc internals manual
lives.
I would not be averse to moving the entire internals manual to the web
in some form. But having it in two places does not seem like a good
idea to me.
Ian
next prev parent reply other threads:[~2008-06-12 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 18:47 Diego Novillo
2008-06-12 19:54 ` Ian Lance Taylor [this message]
2008-06-13 19:24 ` Mark Mitchell
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=m3skviqvny.fsf@google.com \
--to=iant@google.com \
--cc=dnovillo@google.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).