From: "Tomasz Kłoczko via Gdb" <gdb@sourceware.org>
To: Joseph Myers <josmyers@redhat.com>
Cc: Simon Marchi <simark@simark.ca>, Sam James <sam@gentoo.org>,
gdb@sourceware.org
Subject: Re: gdb and ancient GNU autotools
Date: Tue, 27 Feb 2024 20:57:34 +0000 [thread overview]
Message-ID: <CABB28CwCmesnSmecvv=Pdpzx+bXirA4uV+zyHyiVB-NH9Ms6qQ@mail.gmail.com> (raw)
In-Reply-To: <CABB28CwZ8-EB0cq2J1ov7De-CXbb0D-CWtsC6SuqgNhSYtX3nw@mail.gmail.com>
On Tue, 27 Feb 2024 at 20:44, Tomasz Kłoczko <kloczko.tomasz@gmail.com>
wrote:
[..]
> *If no one will try to continue libtool maintenance* atractor anchored in
> libtool will be changing those metrics with time in ONLY ONE DIRECTION
> which will be ONLY more and more affecting gcc, binutils, gdb trio.
>
Only after pressing the "send" button some additional thought bounced
back in my head ..
In gcc, binutils, gdb trio ALREADY is not used OOTB litool and
effectively in those projects source trees effectively are maintained
libtool fork!!!😳
If time on maintaining that tool is already part of those
projects development, why not officially fork it to have 100% control with
less hassles on syncing necessary files across subtrees?🤔
kloczek
--
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH
next prev parent reply other threads:[~2024-02-27 20:58 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 [this message]
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
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='CABB28CwCmesnSmecvv=Pdpzx+bXirA4uV+zyHyiVB-NH9Ms6qQ@mail.gmail.com' \
--to=gdb@sourceware.org \
--cc=josmyers@redhat.com \
--cc=kloczko.tomasz@gmail.com \
--cc=sam@gentoo.org \
--cc=simark@simark.ca \
/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