public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Lisa M. Opus Goldstein" <opus@gnu.org>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: gcc@gcc.gnu.org
Subject: Re: HEADS UP: GCC manual soon to be printed
Date: Thu, 15 May 2003 14:23:00 -0000	[thread overview]
Message-ID: <20030515142354.GA6521@gnu.org> (raw)
In-Reply-To: <Pine.BSF.4.55.0305140148340.55840@acrux.dbai.tuwien.ac.at>



Dear Gerald,


Thank you for the offical 'heads up' and all your work on updating the
manual.

I will wait until the end of May for the final changes to be added,
and then put the book into production.  Any remaining typos or
typsetting issues found along the way will be sent upstream to you
guys.

Please send me one more 'heads up' after all the final changes are
implemented, and the location of the offical tarball, so I can safely
go ahead with production.


Best Regards,


Lisa M. Goldstein           opus@gnu.org
Managing Editor, GNU Press  www.gnupress.org
Business Manager,           Tel 617-542-5942
Free Software Foundation    Fax 617-542-2652


Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> wrote:
> 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/

-- 


  reply	other threads:[~2003-05-15 14:23 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
2003-05-15 14:23   ` Lisa M. Opus Goldstein [this message]
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=20030515142354.GA6521@gnu.org \
    --to=opus@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).