public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: dj@redhat.com
Cc: gcc@gcc.gnu.org, binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: libiberty docs are in
Date: Thu, 27 Sep 2001 11:49:00 -0000	[thread overview]
Message-ID: <3099-Thu27Sep2001205015+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <200109271657.f8RGvLr28862@greed.delorie.com>

> Date: Thu, 27 Sep 2001 12:57:21 -0400
> From: DJ Delorie <dj@redhat.com>
> 
> It is only temporary.  In case there were bugs, I didn't want to
> burden everyone all at once.  When it's proven stable, I'll add it to
> the default rules.

Thank you!

> > I don't recommend using the full @node lines, like this:
> > 
> >     @node Using,Overview,Top,Top
> 
> I couldn't get the auto-node logic to work right in all places.  If
> you can, that's good!

I tested "make info" after applying the changes I sent, and it built
without any complaints.

The secret is that you need to lay out the subnodes in the same order
as they are listed in the menus.  One of the nodes was out of order,
so I moved it.  I'm guessing that this node is what gave you trouble.

> > [Repeat after me: "it's ``occurrence'', not ``occurance'' ;-)  May I
> > suggest "M-x ispell-comments-and-strings RET"?]
> 
> You may, but I was happy to get what was available in place...  :-)

Oops, sorry, I didn't realize you've written the text in the *.c files
as well.  I should have looked in the Changelog before releasing silly
jokes.

> > Index: src/libiberty/libiberty.texi
> 
> Changelog entry?

Here:

2001-09-27  Eli Zaretskii  <eliz@is.elta.co.il>

	* libiberty.texi: (Top level): Add syncodeindex pg.
	(many nodes): Lose the next,prev,up pointers on the @nide line.
	(Using, Supplemental Functions, Replacement Functions): Fix
	markup.
	(Functions): Move around, to allow makeinfo to build the manual
	without next,prev,up pointers in thye node lines.
	(Licenses): Fix typos.

	* index.c, rindex.c, strchr.c, strerror.c, strrchr.c, strstr.c,
	strtol.c, xatexit.c, xexit.c, xmalloc.c: Fix spelling and markup.

	* copying-lib.texi: Lose the next,prev,up pointers on the @node
	line.

  reply	other threads:[~2001-09-27 11:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26 11:56 DJ Delorie
2001-09-27  3:18 ` Eli Zaretskii
2001-09-27  9:57   ` DJ Delorie
2001-09-27 11:49     ` Eli Zaretskii [this message]
2001-09-27 12:58       ` DJ Delorie
2001-09-27 12:07     ` Eli Zaretskii
2001-09-27 12:01   ` Phil Edwards
2001-09-27 13:12     ` DJ Delorie
2001-09-27 13:15       ` Phil Edwards
2001-09-27 13:54     ` Eli Zaretskii
2001-09-27  3:20 ` 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=3099-Thu27Sep2001205015+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).