From: DJ Delorie <dj@redhat.com>
To: eliz@is.elta.co.il
Cc: gcc@gcc.gnu.org, binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: libiberty docs are in
Date: Thu, 27 Sep 2001 12:58:00 -0000 [thread overview]
Message-ID: <200109271957.f8RJvip22590@greed.delorie.com> (raw)
In-Reply-To: <3099-Thu27Sep2001205015+0300-eliz@is.elta.co.il>
I combined your patches and committed them. Thanks!
> 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.
Ok, although this rearranges the chapters also, putting obstacks
before the reference to libiberty-specific functions. I guess it
doesn't matter.
> Oops, sorry, I didn't realize you've written the text in the *.c
> files as well.
Half the docs came from Phil's libiberty.texi. I broke out the bits
and put them in *.c. The other half were manually converted from the
man-like plain text documentation already in *.c.
2001-09-27 Eli Zaretskii <eliz@is.elta.co.il>
* libiberty.texi: (Top level): Add syncodeindex pg. Add
@dircategory and @direntry directives. Add @finalout.
(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.
* functions.texi: Regenerate.
* copying-lib.texi: Lose the next,prev,up pointers on the @node
line.
next prev parent reply other threads:[~2001-09-27 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 11:56 DJ Delorie
2001-09-27 3:20 ` Eli Zaretskii
[not found] ` <1659-Thu27Sep2001121904+0300-eliz@is.elta.co.il>
2001-09-27 9:57 ` DJ Delorie
2001-09-27 12:07 ` Eli Zaretskii
[not found] ` <3099-Thu27Sep2001205015+0300-eliz@is.elta.co.il>
2001-09-27 12:58 ` DJ Delorie [this message]
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
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=200109271957.f8RJvip22590@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=eliz@is.elta.co.il \
--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