Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doc/branch too] Texinfo problems
Date: Tue, 31 Jul 2001 01:39:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010731113947.1042E-100000@is> (raw)
In-Reply-To: <20010730120653.A2876@nevyn.them.org>

On Mon, 30 Jul 2001, Daniel Jacobowitz wrote:

> 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.

How does it get munged?

> I assume & is a legal character here?

The Texinfo manual doesn't say anything about characters that are
invalid in @dircategory, and I don't see anything in makeinfo's code
which would treat & specially, except maybe under --html.

> In any case, Debian happens to use Development

I don't understand that: what ``Development'' did you refer to here?

What does "makeinfo --version" print?

> 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?

Yes, thanks.

> -- 
> 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-31  1:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 12:06 Daniel Jacobowitz
2001-07-31  1:39 ` Eli Zaretskii [this message]
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=Pine.SUN.3.91.1010731113947.1042E-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=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