From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCHSET] [4/4] Fix various issue in TUI
Date: Mon, 19 Jan 2015 16:54:00 -0000 [thread overview]
Message-ID: <20150119165451.GH4041@adacore.com> (raw)
In-Reply-To: <83r3uqybww.fsf@gnu.org>
> Btw, what is the reason we insist on that particular version of
> Autoconf, and not on "2.64 or later"? It's a pain to have an old
> version installed (already there are packages for which 2.65 is too
> old).
I am not absolutely certain. I have a feeling from past experience
that upgrading to new versions is not necessarily a big deal, but
something that needs to be done with care, as it might not work
with new versions of configure. I know that I accidently used
a newer version of configuring in the past, and got errors, so
it doesn't always work, at least for me.
But other than that, one of my reasons is that we know it works, and
using the exact version also allows you to generate changes that are
directly related to your changes and only your changes - which makes
reviewing the patch for the generated file a little easier.
--
Joel
next prev parent reply other threads:[~2015-01-19 16:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 17:56 Eli Zaretskii
2015-01-05 19:55 ` Pedro Alves
2015-01-05 20:06 ` Eli Zaretskii
2015-01-17 9:55 ` Eli Zaretskii
2015-01-19 14:50 ` Joel Brobecker
2015-01-19 16:26 ` Eli Zaretskii
2015-01-19 16:54 ` Joel Brobecker [this message]
2015-01-19 15:43 ` Joel Brobecker
2015-01-19 17:31 ` Eli Zaretskii
2015-01-19 17:54 ` Joel Brobecker
2015-01-22 12:07 ` Pedro Alves
2015-01-22 16:26 ` Eli Zaretskii
2015-01-22 17:15 ` Pedro Alves
2015-01-22 17:30 ` Eli Zaretskii
2015-01-22 18:36 ` Pedro Alves
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=20150119165451.GH4041@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@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