From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 5.1, which texinfo version?
Date: Tue, 24 Jul 2001 03:35:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010724133641.1341J-100000@is> (raw)
In-Reply-To: <3B5C90C3.1020300@cygnus.com>
On Mon, 23 Jul 2001, Andrew Cagney wrote:
> Part of the song and dance of doing a release is sanity checking that
> the info pages can be re-build using all versions of texinfo. For 5.0
> that included 3.12f(?1) and 4.0.
>
> I'm going to work on the assumption that 5.1 is the same and then, post
> 5.1, GDB can switch to requiring >=4.0. Sound ok?
IMHO, we could assume 4.0 even for GDB 5.1. Texinfo 4.0 was released
a year and a half ago, and there's the v4.0c pretest already on
alpha.gnu. So it would appear that 3.x is _way_ obsolete by now.
If we decide to assume 4.0 now, it doesn't really require us to take
any action, except stop testing with 3.12f. We could delay the
cleanup of the ugly hacks we put into the Texinfo sources until 5.2.
next prev parent reply other threads:[~2001-07-24 3:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 14:01 Andrew Cagney
2001-07-24 3:35 ` Eli Zaretskii [this message]
2001-07-24 17:18 ` Andrew Cagney
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=Pine.SUN.3.91.1010724133641.1341J-100000@is \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--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