From: Tom Tromey <tom@tromey.com>
To: "Tomasz Kłoczko via Gdb" <gdb@sourceware.org>
Cc: "Sam James" <sam@gentoo.org>,
"Tomasz Kłoczko" <kloczko.tomasz@gmail.com>
Subject: Re: gdb and ancient GNU autotools
Date: Tue, 27 Feb 2024 08:25:31 -0700 [thread overview]
Message-ID: <87r0gyudxw.fsf@tromey.com> (raw)
In-Reply-To: <CABB28Cw3r4n2o9HRfEYTbT+BrWF+8bF8=AKEg1tdJcapQ8Tnpw@mail.gmail.com> ("Tomasz =?utf-8?Q?K=C5=82oczko?= via Gdb"'s message of "Sat, 24 Feb 2024 18:30:42 +0000")
>>>>> "Tomasz" == Tomasz Kłoczko via Gdb <gdb@sourceware.org> writes:
Tomasz> Why those repos are not moved yet to github or even own instance of the
Tomasz> gitlab to provide OOTB proper cross refs between commits, discussions
Tomasz> MRs/PRs, issue tickets and commit comments for me is kind of a mystery ..
The reason is that GNU has a policy against this. You may disagree with
it but it shouldn't be a mystery. I agree that better tooling here
would be desirable. However, my view is that it's not going to happen.
Tomasz> Going back to the subject: someone at least started thinking about starting
Tomasz> doing something to move away from those ancient GNU autotools versions
Tomasz> (probably kicking a few as*ess on integrating properly some
Tomasz> libtool changes) or move to meson/cmake?
It's a colossal job with a modest payoff. It's also difficult
politically as you must get all the relevant groups on-board before
starting. I personally have other windmills at which to tilt.
Tom
next prev parent reply other threads:[~2024-02-27 15:26 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 [this message]
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
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=87r0gyudxw.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@sourceware.org \
--cc=kloczko.tomasz@gmail.com \
--cc=sam@gentoo.org \
/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