From: Joel Brobecker <brobecker@adacore.com>
To: Luis Machado <luis.machado@arm.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: starting the GDB 14 release process
Date: Wed, 26 Jul 2023 08:26:45 -0700 [thread overview]
Message-ID: <ZME7NT1Hc4HDVKSh@adacore.com> (raw)
In-Reply-To: <470fa016-2205-f453-c7d7-5d62ea9333d1@arm.com>
Hi Luis,
> Although not a blocker for the release, I'd like to include the
> AArch64 SME and SME2 support for the GDB 14 release.
OK.
> Should I create tickets for those or would this be OK to track less
> formally?
PRs are not requirements for this stage, but they do make it a lot easier
for me to keep track of the status, especially if you remember to use
those PRs in the commit message, and also if you cross-ref discussions
in the PR. So, if it's not too much extra work for you, that would be
super useful.
--
Joel
next prev parent reply other threads:[~2023-07-26 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 15:23 Joel Brobecker
2023-07-24 8:23 ` Luis Machado
2023-07-26 15:26 ` Joel Brobecker [this message]
2023-07-27 12:00 ` Luis Machado
2023-07-26 15:36 ` Tom Tromey
2023-07-26 15:44 ` Joel Brobecker
2023-07-26 18:31 ` John Baldwin
2023-07-27 2:44 ` Joel Brobecker
2023-07-27 15:43 ` John Baldwin
2023-09-06 2:19 ` 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=ZME7NT1Hc4HDVKSh@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
/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).