From: Daniel Jacobowitz <drow@mvista.com>
To: fnf@ninemoons.com
Cc: gdb@sources.redhat.com
Subject: Re: Why autoconf 2.13?
Date: Wed, 10 Apr 2002 17:41:00 -0000 [thread overview]
Message-ID: <20020410204103.A3222@nevyn.them.org> (raw)
In-Reply-To: <200204110039.g3B0dCT03033@fred.ninemoons.com>
On Wed, Apr 10, 2002 at 05:39:12PM -0700, Fred Fish wrote:
> Is there some reason that gdb is using a 3 year old version of
> autoconf instead of the latest official FSF release (2.53 I think)?
>
> -Fred
Because all the rest of sourceware is. Every so often there are noises
made about moving forward, but 2.53 and 2.13 aren't even mostly
compatible in practice.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-11 0:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 17:38 Fred Fish
2002-04-10 17:41 ` Daniel Jacobowitz [this message]
2002-04-10 17:47 ` Christopher Faylor
2002-04-11 11:30 ` DJ Delorie
2002-04-11 15:00 ` Tom Tromey
2002-04-11 16:00 ` DJ Delorie
2002-04-12 3:14 ` Andreas Schwab
2002-04-12 8:19 ` DJ Delorie
2002-04-12 8:45 ` Andreas Schwab
2002-04-12 9:07 ` 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=20020410204103.A3222@nevyn.them.org \
--to=drow@mvista.com \
--cc=fnf@ninemoons.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