Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: gdb-patches@sources.redhat.com
Subject: [rfa/doc/branch too] Texinfo problems
Date: Mon, 30 Jul 2001 12:06:00 -0000	[thread overview]
Message-ID: <20010730120653.A2876@nevyn.them.org> (raw)

While building Debian gdb packages, I ran into two problems.  One is, I
think, a problem in Debian's tools rather than gdb; the line:

@dircategory Programming & development tools.

gets munged.  I assume & is a legal character here?  I don't know much about
texinfo.  In any case, Debian happens to use Development, so I'll just
override that.

What's more annoying is this:

install-info --quiet --section 'Programming #SECTION# development tools.'
    'Programming #SECTION# development tools.' /usr/share/info/gdbint.info
install-info: warning, ignoring confusing INFO-DIR-ENTRY in file.

I think the patch below is correct.  OK to commit, trunk and branch?

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

2001-07-30  Daniel Jacobowitz  <drow@mvista.com>

	* gdbint.texinfo: Remove extraneous START-INFO-DIR-ENTRY
	and END-INFO-DIR-ENTRY.

Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.32
diff -u -r1.32 gdbint.texinfo
--- gdbint.texinfo      2001/07/24 10:35:42     1.32
+++ gdbint.texinfo      2001/07/30 19:04:14
@@ -3,9 +3,7 @@
 @include gdb-cfg.texi
 @dircategory Programming & development tools.
 @direntry
-START-INFO-DIR-ENTRY
 * Gdb-Internals: (gdbint).     The GNU debugger's internals.
-END-INFO-DIR-ENTRY
 @end direntry

 @ifinfo


             reply	other threads:[~2001-07-30 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 12:06 Daniel Jacobowitz [this message]
2001-07-31  1:39 ` Eli Zaretskii
2001-07-31 10:24   ` Daniel Jacobowitz

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=20010730120653.A2876@nevyn.them.org \
    --to=dmj+@andrew.cmu.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