From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: "Lisa M. Opus Goldstein" <opus@gnu.org>, gcc@gcc.gnu.org
Subject: Re: HEADS UP: GCC manual soon to be printed
Date: Thu, 15 May 2003 10:22:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.55.0305140148340.55840@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <Pine.BSF.4.53.0304020007270.84822@acrux.dbai.tuwien.ac.at>
On Wed, 2 Apr 2003, Gerald Pfeifer wrote:
> Lisa M. Opus Goldstein, who is Managing Editor, GNU Press, contacted
> me because the GCC manuals are out of print at the FSF and she plans
> to print a new edition in this spring.
Lisa, today we released GCC 3.3 and most of the changes we had planned
for the GCC manuals are now in; the remaining ones should follow by the
end of next week or so. What is your current schedule concerning the
printing of the book(s)?
If anybody has outstanding changes which s/he would like to apply to the
3.3-branch, especially before the manuals are printed by the FSF, please
try to get them in ASAP.
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/
next prev parent reply other threads:[~2003-05-15 10:22 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
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 [this message]
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=Pine.BSF.4.55.0305140148340.55840@acrux.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gcc.gnu.org \
--cc=opus@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).