From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: GDB 12 preparation and target date?
Date: Wed, 26 Jan 2022 08:07:22 -0700 [thread overview]
Message-ID: <87zgnia639.fsf@tromey.com> (raw)
In-Reply-To: <Ye01Pk+wvX77Hf0V@adacore.com> (Joel Brobecker via Gdb-patches's message of "Sun, 23 Jan 2022 15:00:14 +0400")
Joel> - GDB 12 branching 2 months from now (~Mar 20-25);
Joel> - GDB 12.1 release 2 weeks later, so early Apr.
Joel> In terms of patches, I think it would be useful to start listing
Joel> the fixes and enhancements we'd like to include in GDB 12, and
Joel> keep track of them. If possible, it helps if the patches have
Joel> a corresponding GDB PR with the the target milestone set to 12.1.
Joel> Let me know what you guys think, and also please let us know what
Joel> patches you think should be included in GDB 12, and why they are
Joel> important.
I personally wouldn't mind it even a bit sooner, but this plan is also
fine by me.
As for patches, I guess it would be good if we could get through the
backlog of unreviewed patches, at least those not from global
maintainers. Not that all of these could land, but at least they could
be not in limbo.
Tom
next prev parent reply other threads:[~2022-01-26 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 11:00 Joel Brobecker
2022-01-26 15:07 ` Tom Tromey [this message]
2022-01-27 3:54 ` Joel Brobecker
2022-01-28 3:03 ` Tiezhu Yang
2022-01-28 9:40 ` Aktemur, Tankut Baris
2022-02-02 17:00 ` Andrew Burgess
2022-02-02 19:31 ` John Baldwin
2022-02-13 14:33 ` Joel Brobecker
2022-02-14 18:51 ` John Baldwin
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=87zgnia639.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).