From: Luis Machado <luis.machado@arm.com>
To: Joel Brobecker <brobecker@adacore.com>, Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 13.2 and GDB 14 releases...
Date: Tue, 2 May 2023 10:23:03 +0100 [thread overview]
Message-ID: <feeb00bb-3a3c-f766-46b1-370447bb9e12@arm.com> (raw)
In-Reply-To: <ZE/TlICUiUu7zjiF@adacore.com>
On 5/1/23 15:58, Joel Brobecker via Gdb-patches wrote:
> 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?
>
Sounds good to me as well.
next prev parent reply other threads:[~2023-05-02 9:23 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
2023-05-01 16:39 ` Simon Marchi
2023-05-02 9:23 ` Luis Machado [this message]
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=feeb00bb-3a3c-f766-46b1-370447bb9e12@arm.com \
--to=luis.machado@arm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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).