Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
	Joel Brobecker <brobecker@adacore.com>,
	gdb-patches@sourceware.org
Subject: Re: NEED FEEDBACK: time to start the GDB 8.2 release process (2018-05-30 update)
Date: Thu, 31 May 2018 18:35:00 -0000	[thread overview]
Message-ID: <1c44c27f-415e-1b10-bc88-411cf9e0fe20@redhat.com> (raw)
In-Reply-To: <1527789960.1703.12.camel@skynet.be>

On 05/31/2018 07:06 PM, Philippe Waroquiers wrote:
> On Wed, 2018-05-30 at 15:53 -0700, Joel Brobecker wrote:
>> Does anyone have projects that are nearly finished and would be
>> important to include in 8.2 rather than wait for 8.3? If yes,
>> what kind of time frame can we expect for getting those in.
>> Should we wait for the patch to be in master before we cut the branch,
>> or can the changes be backported afterwards?
> 
> If possible, I would like to include 
> https://sourceware.org/ml/gdb-patches/2018-05/msg00462.html
> ('frame apply COMMAND', enhance 'thread apply COMMAND').
> 
> It is (supposed to be) ready :
>   * doc reviewed and OK-ed by Eli
>   * a first code review by Simon (I think I handled/clarified
>     all comments).

Does it include testcases already?

Thanks,
Pedro Alves


  reply	other threads:[~2018-05-31 18:20 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 [this message]
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

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=1c44c27f-415e-1b10-bc88-411cf9e0fe20@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    /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