From: Eli Zaretskii <eliz@gnu.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: jeremy.bennett@embecosm.com, gdb-patches@sourceware.org
Subject: Re: Patch to update gdbint.texinfo [01/04]
Date: Sat, 21 Mar 2009 18:27:00 -0000 [thread overview]
Message-ID: <u4oxmpyqi.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0903211651030.22592@digraph.polyomino.org.uk>
> Date: Sat, 21 Mar 2009 16:54:05 +0000 (UTC)
> From: "Joseph S. Myers" <joseph@codesourcery.com>
> cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
>
> On Sat, 21 Mar 2009, Jeremy Bennett wrote:
>
> > It could be connected with the move to replace etex by a link to pdftex
> > in recent Linuxes (I'm using FC9), which may require some modification
> > to GDB's custom texinfo.tex.
>
> I don't think it's a custom one; there's a single copy of texinfo.tex in
> the src tree, texinfo/texinfo.tex, which is over five years old (version
> 2004-02-19.09). It might be time to replace it with the current version
> (right now, 2009-03-20.13) whether or not it is the cause of problems, as
> long as the current version doesn't break things itself.
Replacing texinfo.tex with the latest version would be fine with me.
next prev parent reply other threads:[~2009-03-21 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 11:21 Jeremy Bennett
2009-03-21 9:34 ` Eli Zaretskii
2009-03-21 10:30 ` Jeremy Bennett
[not found] ` <1237628038.3044.105.camel@thomas>
2009-03-21 12:14 ` Eli Zaretskii
2009-03-21 14:39 ` Jeremy Bennett
2009-03-21 15:58 ` Eli Zaretskii
2009-03-21 17:33 ` Joseph S. Myers
2009-03-21 18:27 ` Eli Zaretskii [this message]
2009-03-21 20:21 ` Jeremy Bennett
2009-03-22 14:24 ` Eli Zaretskii
2009-04-21 12:38 ` Joseph S. Myers
2009-04-21 18: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=u4oxmpyqi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jeremy.bennett@embecosm.com \
--cc=joseph@codesourcery.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