From: Tom Tromey <tom@tromey.com>
To: Andrew Pinski via Gdb <gdb@sourceware.org>
Cc: "Tomasz Kłoczko" <kloczko.tomasz@gmail.com>,
"Andrew Pinski" <pinskia@gmail.com>
Subject: Re: gdb and ancient GNU autotools
Date: Tue, 27 Feb 2024 08:27:30 -0700 [thread overview]
Message-ID: <87msrmudul.fsf@tromey.com> (raw)
In-Reply-To: <CA+=Sn1nJJpJhyb=VWYXF_uqMKVetkAUXqa6eB=ud8BXt=FVPXQ@mail.gmail.com> (Andrew Pinski via Gdb's message of "Sun, 25 Feb 2024 16:58:45 -0800")
>>>>> "Andrew" == Andrew Pinski via Gdb <gdb@sourceware.org> writes:
Andrew> Yes they have not updated to 2.70 or 2.72 yet. But with a complex
Andrew> build system as GCC/binutils/gdb, why update to something if it is
Andrew> working.
I don't fully agree with this approach. There's a benefit to upgrading
periodically, which is that it may ease future upgrades -- including
when one is really needed. It's kind of like rebasing, where if you let
a branch sit for too long, suddenly you're in trouble.
That said, the upgrades are kind of a pain (I did one of them in the past).
So, it can be hard to motivate to do them; and given the slow pace of
auto* development, there's not often a need to rush into it.
Tom
prev parent reply other threads:[~2024-02-27 15:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 16:28 Tomasz Kłoczko via Gdb
2024-02-24 16:51 ` Sam James via Gdb
2024-02-24 17:15 ` Tomasz Kłoczko via Gdb
2024-02-24 17:21 ` Sam James via Gdb
2024-02-24 18:30 ` Tomasz Kłoczko via Gdb
2024-02-24 19:31 ` Mark Wielaard
2024-02-25 0:22 ` Tomasz Kłoczko via Gdb
2024-02-25 7:56 ` Mark Wielaard
2024-02-25 8:05 ` Eli Schwartz via Gdb
2024-02-25 10:40 ` Mark Wielaard
2024-02-25 21:19 ` Eli Schwartz via Gdb
2024-02-25 21:50 ` Tomasz Kłoczko via Gdb
2024-02-25 22:20 ` Andreas Schwab
2024-02-25 23:32 ` Mark Wielaard
2024-02-26 0:29 ` Tomasz Kłoczko via Gdb
2024-02-26 0:46 ` Eli Schwartz via Gdb
2024-02-26 0:55 ` Tomasz Kłoczko via Gdb
2024-02-26 11:44 ` Mark Wielaard
2024-02-26 12:13 ` Tomasz Kłoczko via Gdb
2024-02-26 0:26 ` Eli Schwartz via Gdb
2024-02-27 15:25 ` Tom Tromey
2024-02-27 16:37 ` Simon Marchi via Gdb
2024-02-27 17:33 ` Joseph Myers via Gdb
2024-02-27 17:42 ` Tom Tromey
2024-02-27 20:44 ` Tomasz Kłoczko via Gdb
2024-02-27 20:57 ` Tomasz Kłoczko via Gdb
2024-02-27 20:59 ` Sam James via Gdb
2024-02-26 0:58 ` Andrew Pinski via Gdb
2024-02-27 15:27 ` Tom Tromey [this message]
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=87msrmudul.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@sourceware.org \
--cc=kloczko.tomasz@gmail.com \
--cc=pinskia@gmail.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