From: Hector Martin <marcan@marcan.st>
To: Sam James <sam@gentoo.org>, Joel Brobecker <brobecker@adacore.com>
Cc: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: GDB 13.2 and GDB 14 releases...
Date: Tue, 2 May 2023 15:55:20 +0900 [thread overview]
Message-ID: <73ef119f-396e-f0cd-ad5b-b4a8e50783cc@marcan.st> (raw)
In-Reply-To: <87lei8w04k.fsf@gentoo.org>
On 02/05/2023 00.15, Sam James wrote:
>
> Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org> writes:
>
>> Hi Simon,
>>
>>> IMO, it's better to make regular releases than waiting to have a certain
>>> amount of changes. The changes currently in master might not look
>>> important to me, but maybe someone else is eagerly waiting for a
>>> specific fix or feature to be officially released.
>>
>> Thanks for the suggestion. That makes sense too. Do people want us
>> to switch to this kind of approach?
>
> Yeah, I'd definitely appreciate it for Gentoo. In fact, when you sent
> the first email in this thread, I'd just been wondering if I should ask
> about a point release at least.
>
> Distros in general don't need a release to be action-packed (crammed
> full of features), it's better that we get bug fixes out faster and
> not have to worry about cherry-picking ourselves. It also makes
> debugging any regressions a lot easier if the delta is a bit smaller ;)
>
> I've CC'd marcan as well because he recently had some frustration
> working on Asahi Linux when it turned out something had been fixed in
> master a good while ago but hadn't propagated into a release.
Yup. The state of affairs on Apple machines right now is that I am
learning lldb, because gdb is completely broken and crashes immediately
on `run`. This was a 13.1 regression that was fixed upstream a month
ago, but there has been no point fix release since then.
I don't think it's really reasonable to expect downstream distros to
patch software to make it work *at all*. Stuff like this should trigger
a point bugfix release.
- Hector
next prev parent reply other threads:[~2023-05-02 6:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 20:15 Joel Brobecker
2023-05-01 13:37 ` Simon Marchi
2023-05-01 14:58 ` Joel Brobecker
2023-05-01 15:15 ` Sam James
2023-05-02 6:55 ` Hector Martin [this message]
2023-05-01 16:39 ` Simon Marchi
2023-05-02 9:23 ` Luis Machado
2023-05-01 16:16 ` John Baldwin
2023-05-02 12:57 ` Luis Machado
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=73ef119f-396e-f0cd-ad5b-b4a8e50783cc@marcan.st \
--to=marcan@marcan.st \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).