From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Franco de Carvalho <pedromfc@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, uweigand@de.ibm.com
Subject: Re: NEED FEEDBACK: time to start the GDB 8.2 release process (2018-05-30 update)
Date: Mon, 11 Jun 2018 22:52:00 -0000 [thread overview]
Message-ID: <20180611225212.GA31460@adacore.com> (raw)
In-Reply-To: <871sdqkwtt.fsf@linux.vnet.ibm.com>
Hello,
> I'm working on a few patches to enable access to additional registers in
> ppc, which I was hoping to finish in time for 8.2. No patches are ready
> yet, and probably won't be ready in two weeks. I might be able to finish
> them in 3 or 4 weeks. They should be backportable to the branch.
OK. Good to know. In case you're not familiar with the process,
once the branch is cut, you'll need one of the Global Maintainers,
typically the maintainer who reviews your patch, to OK it for
the branch. We would normally only do that if it makes sense.
In particular, we want to make sure that there is very little chance
the branch's stability might be impacted.
In the meantime, we're not ready for the branch, yet, but I will
try to push for it to be created by end of this month.
--
Joel
prev parent reply other threads:[~2018-06-11 22:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 23:09 Joel Brobecker
2018-05-31 9:23 ` Alan Hayward
2018-05-31 18:35 ` Philippe Waroquiers
2018-05-31 18:35 ` Pedro Alves
2018-05-31 21:20 ` Philippe Waroquiers
2018-05-31 19:40 ` Sergio Durigan Junior
2018-06-01 17:27 ` Joel Brobecker
2018-06-01 21:42 ` Pedro Franco de Carvalho
2018-06-11 22:52 ` Joel Brobecker [this message]
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=20180611225212.GA31460@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedromfc@linux.vnet.ibm.com \
--cc=uweigand@de.ibm.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