From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa:doco, 6.0] (C) and other fixes
Date: Mon, 04 Aug 2003 16:21:00 -0000 [thread overview]
Message-ID: <20030804162140.GA28146@nevyn.them.org> (raw)
In-Reply-To: <3F2E85C0.1020504@redhat.com>
On Mon, Aug 04, 2003 at 12:11:44PM -0400, Andrew Cagney wrote:
> Hello,
>
> This little audit fixes a number of problems in the current doco:
>
> - gdbint.texinfo and stabs.texinfo didn't have correct invariant statements
>
> - stabs.texinfo didn't include the FDL
>
> - a stray @bye in agentexpr.texi caused the main manual to loose several
> appendixes and the index :-(
Oh! _Thanks_ for figuring out what was wrong. I built a pdf the other
day, noticed it didn't have an index, and foolishly assumed it hadn't
had one the last time either...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-08-04 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 16:11 Andrew Cagney
2003-08-04 16:21 ` Daniel Jacobowitz [this message]
2003-08-07 4:24 ` Andrew Cagney
2003-08-07 5:08 ` Eli Zaretskii
2003-08-07 21:36 ` Andrew Cagney
2003-08-08 7:33 ` Eli Zaretskii
2003-08-08 13:55 ` Andrew Cagney
2003-08-04 20:29 ` Eli Zaretskii
2003-08-04 20:43 ` Andrew Cagney
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=20030804162140.GA28146@nevyn.them.org \
--to=drow@mvista.com \
--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