Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, t@adacore.com, donb@codesourcery.com,
	Pedro Alves <palves@redhat.com>, Yao Qi <yao.qi@arm.com>,
	antoine.tremblay@ericsson.com
Subject: Re: GDB 7.12 release - 2016-09-21 update?
Date: Wed, 21 Sep 2016 17:52:00 -0000	[thread overview]
Message-ID: <34925d6f8a7c2d4de24d470bad5e51d2@simark.ca> (raw)
In-Reply-To: <20160921171639.GB3842@adacore.com>

On 2016-09-21 13:16, Joel Brobecker wrote:
> Hello everyone,
> 
> Sorry for being radio-silent the last few weeks. It's been a 
> combination
> of a crazy traveling schedule, and that thing we call "work"...
> 
> Anyways, I reviewed the list of PRs marked as targetting 7.12,
> as well as the items listed in our 7.12 release page
> (https://sourceware.org/gdb/wiki/GDB_7.12_Release).
> 
> It looks like we may have a ways to go before being able to release.
> Here are my thoughts on each of them. What do you guys think?

Thanks for doing this, tell us if you need any help for anything.

> PR 20487: Thread sync broken between mi and cli with new-ui command
> 
>         Assigned to: Antoine Tremblay
>         Status: Fix in progress
> 
>         Not sure if this is really blocking for 7.12 either as it
>         relates to a new feature. But since we seem to be close to
>         a resolution, and this makes the new feature more usable,
>         perhaps we can try to have it in 7.12. Otherwise, perhaps
>         release 7.12 with this limitation in the release notes,
>         and fix it for 7.12.1???

I took over this one.  As you said, since it's not a regression, it's 
not critical.  But as there are still other issues to be solved before 
the release, I'll continue to aim to have it in 7.12.  If it happened to 
be the last remaining open issue, it should certainly not block the 
release.

Simon


  reply	other threads:[~2016-09-21 17:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 17:17 Joel Brobecker
2016-09-21 17:52 ` Simon Marchi [this message]
2016-10-03 21:10   ` Simon Marchi
2016-09-21 18:30 ` Don Breazeal
2016-09-22 10:40 ` Yao Qi
2016-09-27 18:16 ` Jan Kratochvil
2016-10-06 12:12 ` Pedro Alves
2016-10-06 14:51   ` Pedro Alves
2016-10-06 16:33     ` Maciej W. Rozycki
2016-10-06 16:41     ` Joel Brobecker
2016-10-07 15:41       ` Pedro Alves
2016-10-07 16: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=34925d6f8a7c2d4de24d470bad5e51d2@simark.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=antoine.tremblay@ericsson.com \
    --cc=brobecker@adacore.com \
    --cc=donb@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=t@adacore.com \
    --cc=yao.qi@arm.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