From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 7.7 branching on Monday?
Date: Wed, 25 Dec 2013 04:48:00 -0000 [thread overview]
Message-ID: <m3ha9xh6xr.fsf@redhat.com> (raw)
In-Reply-To: <20131220032812.GJ3493@adacore.com> (Joel Brobecker's message of "Fri, 20 Dec 2013 07:28:12 +0400")
On Friday, December 20 2013, Joel Brobecker wrote:
>> Now, what do you want me to do? Maybe update the wiki? I hope that the
>> AArch64 patch will be approved very quickly, so maybe I'll even be able
>> to push it this weekend.
>
> I will venture a guess that you'll be able to get this one push
> by Monday, but even if you don't, I think it'll be sufficiently
> contained that we can backport it to the branch.
Hey Joel,
Just a heads-up: the AArch64 patch has been submitted and pre-reviewed
by Yufeng Zhang and Marcus Shawcroft (both from ARM), but I still need a
maintainer's approval to check it in.
I'm not sure I'll get one until next year, when everybody comes back
from the holidays. I saw you're delaying the branch creation until next
week, so let's see what we can do :-). As the last option, as you said,
I can always backport the patch.
Thanks a lot,
--
Sergio
next prev parent reply other threads:[~2013-12-25 4:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 17:59 Joel Brobecker
2013-12-19 18:06 ` H.J. Lu
2013-12-19 18:22 ` Joel Brobecker
2013-12-19 18:27 ` H.J. Lu
2013-12-19 21:52 ` Mark Kettenis
2013-12-19 22:29 ` H.J. Lu
2013-12-19 20:31 ` Sergio Durigan Junior
2013-12-20 3:28 ` Joel Brobecker
2013-12-20 3:37 ` Sergio Durigan Junior
2013-12-25 4:48 ` Sergio Durigan Junior [this message]
2013-12-28 3:11 ` Joel Brobecker
2013-12-23 8:01 ` Joel Brobecker
2014-01-07 2:54 ` Joel Brobecker
2014-01-07 23:44 ` Pierre Muller
2013-12-24 21:22 Nick Bull
2013-12-25 2:47 ` 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=m3ha9xh6xr.fsf@redhat.com \
--to=sergiodj@redhat.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).