From: Andrew Cagney <ac131313@cygnus.com>
To: k_fukui@highway.ne.jp
Cc: Eli Zaretskii <eliz@is.elta.co.il>,
jimb@cygnus.com, gdb@sources.redhat.com, keiths@cygnus.com
Subject: Re: makeinfo problem
Date: Mon, 17 Sep 2001 21:37:00 -0000 [thread overview]
Message-ID: <3BA6CF6D.3060702@cygnus.com> (raw)
In-Reply-To: <200109100726.JAA18488@is.elta.co.il>
>> There's some snafu in the latest version of gdb.texinfo in the CVS on
>> the trunk. Jim, it seems that your commit, which created version
>> 1.50, is the culprit: the text you commited is broken, it looks like
>> some lines just disappeared. See the fragment below.
>>
>> In addition, the new Overlays section is not mentioned at all in the
>> log message.
>
>
> Jim, these problems is still in the CVS, which means someone who does a
> "cvs up" cannot build the current sources.
>
> Could you please fix this ASAP, or at least send me the correct text
> of the Overlays section, so that I could fix it myself?
I believe this has been fixed.
Andrew
prev parent reply other threads:[~2001-09-17 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 7:42 Kaoru Fukui
2001-09-04 8:57 ` Eli Zaretskii
2001-09-10 0:25 ` Eli Zaretskii
2001-09-17 21:37 ` Andrew Cagney [this message]
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=3BA6CF6D.3060702@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=jimb@cygnus.com \
--cc=k_fukui@highway.ne.jp \
--cc=keiths@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