Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] libgdb updates to doco
Date: Fri, 27 Jul 2001 02:36:00 -0000	[thread overview]
Message-ID: <5567-Fri27Jul2001123713+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3B606479.2070205@cygnus.com>

> Date: Thu, 26 Jul 2001 14:42:01 -0400
> From: Andrew Cagney <ac131313@cygnus.com>
> 
> > Texinfo cross-references (and thus index entries) refer to the
> > enclosing node in the Info version, so having smaller nodes makes sure
> > you will land close to the stuff you are looking for.  (There's the
> > new @anchor directive which is free from this limitation, but older
> > Info readers don't support it, so we should not yet use it too much;
> > and index entries don't produce @anchor's anyway.)
> 
> For my part, I was looking for an existing example but couldn't find one 

Just put a @node before each @section and @subsection.  While at that,
consider converting @heading and @subheading into @section and
@subsection, and then apply the first rule again ;-).

> I've checked in the libgdb stuff.  Hmm, whats next?

How about documenting multi-arch so that I could understand how to
multi-arch a target without reading the code? ;-)


  reply	other threads:[~2001-07-27  2:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-25 20:38 Andrew Cagney
2001-07-25 23:51 ` Eli Zaretskii
2001-07-26 11:43   ` Andrew Cagney
2001-07-27  2:36     ` Eli Zaretskii [this message]
2001-07-27 13:36       ` Andrew Cagney
     [not found]         ` <1438-Sat28Jul2001103025+0300-eliz@is.elta.co.il>
2001-07-28  7:50           ` Andrew Cagney
2001-07-28  9:17             ` Eli Zaretskii

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=5567-Fri27Jul2001123713+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@cygnus.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