From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@math.stanford.edu
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] remove dependency of f-exp.tab.c on c-exp.tab.c
Date: Mon, 02 Dec 2002 14:00:00 -0000 [thread overview]
Message-ID: <200212022200.gB2M0he13522@duracef.shout.net> (raw)
> f-exp.y wasn't added until 1994, but presumably it also had the
> artificial dependency included for the same reason; and that
> artificial dependency must have gotten accidentally left behind when
> this issue was cleaned up.
Here is one more bit of history:
# top level ChangeLog
Thu Jul 31 19:49:49 1997 Ian Lance Taylor <ian@cygnus.com>
* ylwrap: New file.
* Makefile.in (DEVO_SUPPORT): Add ylwrap.
... so those funky serialization dependencies existed 3-4 years
before ylwrap fixed the problem in a more robust way.
gdb has more history than the Strand bookstore. :)
Michael C
next reply other threads:[~2002-12-02 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 14:00 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-02 11:33 Michael Elizabeth Chastain
2002-12-02 11:57 ` David Carlton
2002-12-04 15:00 ` David Carlton
2002-12-02 11:13 David Carlton
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=200212022200.gB2M0he13522@duracef.shout.net \
--to=mec@shout.net \
--cc=carlton@math.stanford.edu \
--cc=gdb-patches@sources.redhat.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