From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: start of the GDB 11 release cycle
Date: Tue, 25 May 2021 07:46:13 -0300 [thread overview]
Message-ID: <8a835711-250a-a4bb-dffd-1d0b2e10fca7@linaro.org> (raw)
In-Reply-To: <20210524210218.GD734687@adacore.com>
Joel,
On 5/24/21 6:02 PM, Joel Brobecker wrote:
> Hi 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.
>>
>> Sorry, I dropped the ball on this. Since all of the required patches are on
>> the list being reviewed (I sent them last week), I did not create tickets
>> for those.
>>
>> I think I should still do that to make your life easier though. I'm thinking
>> a single ticket tracking the 4 or 5 patches related to it. Would that work?
>
> Thanks Luis. This would work. That being said, if you prefer giving
> me URLs of the patch series, as long as the subject doesn't change
> from one version to the next, I don't mind following that instead.
> I only mentioned it because you originally proposed to do it that way.
> I would do what's simplest for you.
Here it is:
https://sourceware.org/bugzilla/show_bug.cgi?id=27909
>
>>> Other than that, how is that activity going? Do you feel like you are
>>> making the progress you were hoping for?
>>
>> Yes. The patches are not too big and I got some helpful positive reviews.
>> I'm expecting to be able to push a final version in a week or so.
>
> Nice, well done ;-).
>
next prev parent reply other threads:[~2021-05-25 10:46 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
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 [this message]
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=8a835711-250a-a4bb-dffd-1d0b2e10fca7@linaro.org \
--to=gdb-patches@sourceware.org \
--cc=brobecker@adacore.com \
--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