From: Joel Brobecker <brobecker@adacore.com>
To: Luis Machado <luis.machado@linaro.org>
Cc: gdb-patches@sourceware.org
Subject: Re: start of the GDB 11 release cycle
Date: Mon, 24 May 2021 12:42:15 -0700 [thread overview]
Message-ID: <20210524194215.GB758326@adacore.com> (raw)
In-Reply-To: <995340af-3cef-e322-0887-3a76bc6ad34d@linaro.org>
Hello Luis,
> For issues, I have a couple that I'd like to get fixed for AArch64 MTE
> before GDB 11. I'll file those in bugzilla and will set the fields
> accordingly.
Would you mind creating the bugzilla entries? If you have patches
pending, would you mind also including them in the comment section
of new entries. It'll make it easier for me to keep track of this one
and not forget.
Other than that, how is that activity going? Do you feel like you are
making the progress you were hoping for?
Thank you!
--
Joel
next prev parent reply other threads:[~2021-05-24 19:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 0:04 Joel Brobecker
2021-05-10 3:20 ` Mike Frysinger via Gdb-patches
2021-05-10 22:10 ` Joel Brobecker
2021-05-24 19:40 ` Joel Brobecker
2021-05-25 2:01 ` Mike Frysinger via Gdb-patches
2021-05-26 22:03 ` Joel Brobecker
2021-05-29 15:58 ` Mike Frysinger via Gdb-patches
2021-05-10 3:52 ` Luis Machado via Gdb-patches
2021-05-10 22:11 ` Joel Brobecker
2021-05-11 11:05 ` Luis Machado via Gdb-patches
2021-05-11 17:00 ` Joel Brobecker
2021-05-12 18:15 ` Luis Machado via Gdb-patches
2021-05-24 19:42 ` Joel Brobecker [this message]
2021-05-24 20:27 ` Luis Machado via Gdb-patches
2021-05-24 21:02 ` Joel Brobecker
2021-05-25 10:46 ` Luis Machado via Gdb-patches
2021-05-26 22:04 ` Joel Brobecker
2021-05-10 5:52 ` Bernd Edlinger
2021-05-10 15:10 ` Simon Marchi via Gdb-patches
2021-05-10 16:07 ` Andrew Burgess
2021-05-10 16:57 ` Simon Marchi via Gdb-patches
2021-05-10 22:12 ` Joel Brobecker
2021-05-11 12:45 ` Rainer Orth
2021-05-11 16:57 ` Joel Brobecker
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=20210524194215.GB758326@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@linaro.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