public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
	gcc@gcc.gnu.org, "Lisa M. Opus Goldstein" <opus@gnu.org>
Subject: Re: HEADS UP: GCC manual soon to be printed
Date: Thu, 03 Apr 2003 06:16:00 -0000	[thread overview]
Message-ID: <20030403054803.GC22149@daikokuya.co.uk> (raw)
In-Reply-To: <87znn8e6ed.fsf@egil.codesourcery.com>

Zack Weinberg wrote:-

> Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
> 
> >  3) If you are currently working on changes to the manual(s) or are
> >  aware of pressing issues, please let us know ASAP so that we can
> >  take that into account and try to address them, respectively.
> 
> The CPP manual is out of date in several respects - I have not been
> prioritizing fixing that, but I can bump it up.

What's out of date?

Neil.

  parent reply	other threads:[~2003-04-03  5:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 23:38 Gerald Pfeifer
2003-04-02 20:47 ` Joseph S. Myers
2003-04-03  4:32 ` Zack Weinberg
2003-04-03  5:48   ` Janis Johnson
2003-04-03  6:16   ` Neil Booth [this message]
2003-04-03  7:54     ` Zack Weinberg
2003-04-03  8:39   ` Joseph S. Myers
2003-04-08 19:06 ` Janis Johnson
2003-05-15 10:22 ` Gerald Pfeifer
2003-05-15 14:23   ` Lisa M. Opus Goldstein
2003-05-18 22:31     ` Joseph S. Myers
2003-05-15 22:14   ` Joseph S. Myers
2003-05-21 20:24   ` Joseph S. Myers
2003-05-21 20:28     ` Douglas B Rupp
2003-05-21 20:41       ` Joseph S. Myers
2003-05-23 17:59         ` [PATCH] Remove VMS section in documentation (was Re: HEADS UP: GCC manual soon to be printed) Douglas B Rupp
2003-05-22 19:06     ` HEADS UP: GCC manual soon to be printed Lisa M. Opus Goldstein
2003-05-21 22:17 Stephan T. Lavavej
2003-05-22  3:08 ` Simon Law

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=20030403054803.GC22149@daikokuya.co.uk \
    --to=neil@daikokuya.co.uk \
    --cc=gcc@gcc.gnu.org \
    --cc=opus@gnu.org \
    --cc=pfeifer@dbai.tuwien.ac.at \
    --cc=zack@codesourcery.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).