Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: fix node name (revised patch)
Date: Tue, 28 Oct 2003 22:00:00 -0000	[thread overview]
Message-ID: <vt2znflm3aa.fsf@zenia.home> (raw)
In-Reply-To: <9003-Sat25Oct2003145827+0200-eliz@elta.co.il>

"Eli Zaretskii" <eliz@elta.co.il> writes:

> > From: Jim Blandy <jimb@redhat.com>
> > Date: 24 Oct 2003 22:59:39 -0500
> > 
> > I was trying to figure out why this hasn't bothered anyone yet --- the
> > node name with the single quotes has been in there for months --- and
> > I realized that it is because I'm using an older version of
> > texinfo.tex (circa 1999).
> 
> The real question that we should ask ourselves wrt this is: how come
> your older texinfo.tex was being used instead of the one that comes
> with GDB (which, I hope, is new enough).
> 
> Can you look into this, please?

The reason I'm getting an old texinfo.tex is that I'm building in a
source tree produced by checking out a module from Red Hat's internal
CVS repository that excludes texinfo --- the module contains only
cross-compilation tools, assuming that the user has an appropriate
native toolchain installed on his system already.  Specifically, it
does not contain its own texinfo directory.  So the build gets the
texinfo.tex installed as part of Red Hat 8.0, which says:

\def\texinfoversion{1999-09-25.10}

So there is no underlying problem in GDB's documentation build
process; it is an anomaly introduced by our internal processes.


  reply	other threads:[~2003-10-28 22:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-25  2:41 RFA: fix node name Jim Blandy
2003-10-25  4:00 ` RFA: fix node name (revised patch) Jim Blandy
2003-10-25 13:02   ` Eli Zaretskii
2003-10-25 13:03   ` Eli Zaretskii
2003-10-28 22:00     ` Jim Blandy [this message]
2003-10-29  6:18       ` Eli Zaretskii
2003-10-25 13:00 ` RFA: fix node name 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=vt2znflm3aa.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=eliz@elta.co.il \
    --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