From: Simon Law <sfllaw@engmail.uwaterloo.ca>
To: gcc@gcc.gnu.org
Subject: Re: HEADS UP: GCC manual soon to be printed
Date: Thu, 22 May 2003 03:08:00 -0000 [thread overview]
Message-ID: <20030522023123.GB14154@law.yi.org> (raw)
In-Reply-To: <000101c31fdf$eabfeb00$3c9fd783@northwood>
On Wed, May 21, 2003 at 02:28:22PM -0700, Stephan T. Lavavej wrote:
> [Gerald Pfeifer]
> > 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.
>
> Can the (really) small problems I identified here:
> http://gcc.gnu.org/ml/gcc/2003-05/msg01895.html
> be fixed in time for the printed manuals?
>
> I would write a patch myself, but I don't know how that process works (even
> though I recently learned how to use diff and patch).
I will prepare a patch, which Jim Morrison will forward to the
GCC documentation people.
Simon
next prev parent reply other threads:[~2003-05-22 2:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 22:17 Stephan T. Lavavej
2003-05-22 3:08 ` Simon Law [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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-22 19:06 ` Lisa M. Opus Goldstein
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=20030522023123.GB14154@law.yi.org \
--to=sfllaw@engmail.uwaterloo.ca \
--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).