From: Joe Buck <jbuck@synopsys.com>
To: martin@mira.isdn.cs.tu-berlin.de (Martin von Loewis)
Cc: rjoiner@tc.net, N8TM@aol.com, egcs@cygnus.com
Subject: Re: Huh?
Date: Sat, 24 Oct 1998 12:12:00 -0000 [thread overview]
Message-ID: <199810241911.MAA08002@atrus.synopsys.com> (raw)
In-Reply-To: <199810232137.WAA25253@mira.isdn.cs.tu-berlin.de>
> The makefile will call bison if the C code is absent or
> out-of-date. I'm not sure which one happened in the snapshot, I'm sure
> this was a mistake, though.
It has been a frequent occurrence that snapshots or even releases
have out-of-date derived files (outputs of bison or makeinfo).
> Regards,
> Martin
>
next prev parent reply other threads:[~1998-10-24 12:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <435ded07.362ec94c@aol.com>
1998-10-22 21:15 ` Huh? Randy Joiner
1998-10-23 14:37 ` Huh? Martin von Loewis
1998-10-24 12:12 ` Joe Buck [this message]
1998-10-26 6:26 ` regenerating dependent files on checkin [was Re: Huh?] Dave Love
1998-10-26 21:00 ` Jeffrey A Law
1998-10-21 19:20 Huh? TTK Ciar
-- strict thread matches above, loose matches on Subject: below --
1998-10-21 11:41 Huh? Randy Joiner
1998-10-21 22:10 ` Huh? Per Bothner
1997-08-29 21:09 Huh? Jim Wilson
1997-08-22 19:23 Huh? Peter Gerwinski
1997-08-19 17:54 Huh? Peter Seebach
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=199810241911.MAA08002@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=N8TM@aol.com \
--cc=egcs@cygnus.com \
--cc=martin@mira.isdn.cs.tu-berlin.de \
--cc=rjoiner@tc.net \
/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).