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: Wed, 12 May 2021 15:15:38 -0300 [thread overview]
Message-ID: <33bfd501-4d7d-dbfc-6c98-32d941730c6d@linaro.org> (raw)
In-Reply-To: <20210511170005.GM3261@adacore.com>
Joel,
On 5/11/21 2:00 PM, Joel Brobecker wrote:
>> I have an implementation I can send within a couple weeks. From the kernel's
>> side, we just need to agree on the core file format.
>>
>> So my guesstimate is 3 to 4 weeks.
>
> Alright. Let's see how it goes. I'm thinking that if this is still
> ongoing by the time we are otherwise ready to create the branch,
> we can go ahead with the branch, and then backport your changes
> afterwards. Normally, the risk should be fairly low and limited
> to just this target.
Sounds reasonable. I expect the impact will be small indeed. I'll try to
expedite this.
next prev parent reply other threads:[~2021-05-12 18:15 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 [this message]
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
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=33bfd501-4d7d-dbfc-6c98-32d941730c6d@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