public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: ccorn@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: wwwdocs/htdocs/gcc-3.2 index.html Date: Thu, 06 Feb 2003 23:26:00 -0000 [thread overview] Message-ID: <20030206232627.18483.qmail@sources.redhat.com> (raw) Files modified in the GCC repository. Log entry: Add 3.2.2 release information. Structure content into two sections: "Release History" and "References and Acknowledgements". Thus get rid of the "see below"-style reference. Add references to the current release information and to the complete changes page at the top. Use description lists for the revision history.
next reply other threads:[~2003-02-06 23:26 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-06 23:26 ccorn [this message] -- strict thread matches above, loose matches on Subject: below -- 2019-06-09 19:30 gerald 2018-08-27 4:20 gerald 2016-09-30 13:17 redi 2014-06-28 7:46 gerald 2008-07-26 19:54 gerald 2006-03-09 22:46 gerald 2003-04-25 7:58 gerald 2003-02-07 16:15 gerald 2003-02-07 16:10 gerald 2003-02-07 8:04 gerald 2003-02-07 8:04 gerald 2003-02-07 7:57 gerald 2002-11-18 23:48 mmitchel
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=20030206232627.18483.qmail@sources.redhat.com \ --to=ccorn@gcc.gnu.org \ --cc=gcc-cvs-wwwdocs@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: linkBe 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).