From: Bruce Korb <korbb@datadesign.com>
To: egcs@cygnus.com
Subject: Re: Patch for memory blowup
Date: Fri, 12 Dec 1997 07:40:00 -0000 [thread overview]
Message-ID: <34915A5D.4B28@datadesign.com> (raw)
In-Reply-To: <199712120113.RAA26139@supernova.earthlink.net>
Mark Mitchell wrote:
...
> The diffs below look longer than they are due to an indentation change
> that happened when a set of curly braces went away. Fred's program:
...
> Index: gcc/toplev.c
> ===================================================================
> RCS file: /home/mitchell/Repository/egcs/gcc/toplev.c,v
> retrieving revision 1.1.1.4
> diff -c -p -r1.1.1.4 toplev.c
> *** toplev.c 1997/12/08 07:30:40 1.1.1.4
> --- toplev.c 1997/12/12 00:09:17
Try using:
diff -cwb -p -r1.1.1.4 toplev.c
--
Bruce Korb | Data Design Systems, Inc.
Korbb at DataDesign dot com | 45 Cabot Dr., Suite 110
Voice: 408-260-0280 | Santa Clara, CA 95051
Fax: 408-260-0281 | USA
next prev parent reply other threads:[~1997-12-12 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-11 17:11 Mark Mitchell
1997-12-11 22:59 ` Mark Mitchell
1997-12-15 10:37 ` Jeffrey A Law
1997-12-11 23:55 ` Tudor Hulubei
1997-12-12 7:40 ` Bruce Korb [this message]
1997-12-12 7:49 ` Jeffrey A Law
1997-12-12 10:18 ` Mark Mitchell
1997-12-12 17:52 Peter Schmid
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=34915A5D.4B28@datadesign.com \
--to=korbb@datadesign.com \
--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).