From: H.J. Lu <hjl@lucon.org>
To: egcs@cygnus.com
Subject: Re: A prototype patch for tree.h/tree.def/calls.c
Date: Tue, 19 Aug 1997 13:19:51 -0000 [thread overview]
Message-ID: <m0x0opG-0004edC@ocean.lucon.org> (raw)
In-Reply-To: 12479.871967281@hurl.cygnus.com
>
> In message <m0x0cfX-0004edC@ocean.lucon.org>you write:
> > Hi,
> >
> > Here is a patch for tree.h/tree.h/calls.c. I hope it will
> > be installed soon. Otherwise, it will be very hard to submit
> > clean patches. Thanks.
> See my comments from your last patch. They apply to this patch
> too. If you address those problems I'll install both patchkits.
>
I have some problem s with my emails for the past few days. I may
have lost some. I only remember your comments on BUFSIZ being a macro,
which turned out ok. What else?
Thanks.
--
H.J. Lu (hjl@gnu.ai.mit.edu)
next reply other threads:[~1997-08-19 13:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-19 13:19 H.J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-08-19 21:22 Ian Haggard
1997-08-19 19:24 Ugly *.def in gcc H.J. Lu
1997-08-19 19:45 ` A prototype patch for tree.h/tree.def/calls.c Jeffrey A Law
1997-08-19 19:12 H.J. Lu
1997-08-19 19:00 Some Haifa scheduler bugs Jeffrey A Law
1997-08-19 19:00 ` A prototype patch for tree.h/tree.def/calls.c Jeffrey A Law
1997-08-19 19:00 ` H.J. Lu
1997-08-19 19:00 H.J. Lu
1997-08-19 19:00 ` Jeffrey A Law
1997-08-19 17:54 H.J. Lu
1997-08-19 17:52 John Carr
1997-08-19 17:43 D.V. Henkel-Wallace
1997-08-19 16:06 egcs: A new compiler project to merge the existing GCC forks H.J. Lu
1997-08-19 16:06 ` A prototype patch for tree.h/tree.def/calls.c Jeffrey A Law
1997-08-19 3:52 egcs: A new compiler project to merge the existing GCC forks (fwd) H.J. Lu
1997-08-19 5:08 ` A prototype patch for tree.h/tree.def/calls.c Jeffrey A Law
1997-08-18 23:56 H.J. Lu
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=m0x0opG-0004edC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.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).