Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Keith Seitz <keiths@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch 0/3] Re: [RFA] c++/11734 revisited (and c++/12273)
Date: Thu, 17 Mar 2011 13:21:00 -0000	[thread overview]
Message-ID: <20110317124128.GX31264@adacore.com> (raw)
In-Reply-To: <20110317031911.GA13470@host1.jankratochvil.net>

> > Does it mean that we should be good to go for the 7.2.1 release soon?
> 
> There is yet
> 	Re: [RFA] c++/12506
> 	http://sourceware.org/ml/gdb-patches/2011-03/msg00742.html
> 
> which is also a physname regression and the fix is not anything large IMO.

Thanks for pointing this one out. I've added it to both 7.2 & 7.3
checklists.

> > It seems that finding these fixes have been a bit long and treacherous,
> > so we may want to think twice about putting it in 7.2 (?);
> 
> as 7.3 should be released soon with all the delays on 7.2.x I am no longer
> sure how much valid is the 7.2.x release now.

I'm with you on the relative usefulness of producing a 7.2.1, and
I'm not sure that I would use it myself or not.  So I'm happy to
drop this release. But it's only about an hour of my time, so I am
also just as happy making it, if it's useful to someone.

For 7.3, we still have a few extra items to take care of:
  * Merge your work on the ifunc branch
  * Pedro's <unavailable> value support
  * NEWS & Manual checks (easy and probably fast)

Once this is done, we can branch, and produce our first RC, but it's
then at least another 2 weeks before we produce the first release.
So, I'm going to venture a guess that we're still, say, 4 weeks away
from release.

-- 
Joel


  reply	other threads:[~2011-03-17 12:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09  0:50 [RFA] c++/11734 revisited Keith Seitz
2010-12-09  4:02 ` Eli Zaretskii
2010-12-09 21:45 ` Tom Tromey
2010-12-09 21:52   ` Jan Kratochvil
2010-12-10 15:21     ` Keith Seitz
2010-12-14 20:03   ` Keith Seitz
2011-01-24 18:15     ` Jan Kratochvil
2011-01-26 23:14       ` Jan Kratochvil
2011-02-06 22:04     ` Jan Kratochvil
2011-02-06 22:45     ` [patch 0/3] Re: [RFA] c++/11734 revisited (and c++/12273) Jan Kratochvil
2011-02-08 21:42       ` Tom Tromey
2011-02-10 21:45       ` Keith Seitz
2011-02-17 18:37         ` Keith Seitz
2011-02-18  3:24           ` Keith Seitz
2011-02-21 11:41           ` Jan Kratochvil
2011-02-24 20:41             ` Keith Seitz
2011-02-27 21:18             ` Jan Kratochvil
2011-03-01 22:00               ` Keith Seitz
2011-03-14  7:52                 ` Jan Kratochvil
2011-03-15 19:03                   ` Keith Seitz
2011-03-16  8:28                     ` Jan Kratochvil
2011-03-16 13:58                       ` Tom Tromey
2011-03-16 23:20                       ` Keith Seitz
2011-03-17  3:19                         ` Joel Brobecker
2011-03-17  9:11                           ` Jan Kratochvil
2011-03-17 13:21                             ` Joel Brobecker [this message]
2011-02-06 22:46     ` [patch 1/3] revert physname part (b) [Re: [RFA] c++/11734 revisited] Jan Kratochvil
2011-02-06 22:46     ` [patch 3/3] Various linespec fixups " Jan Kratochvil
2011-02-06 22:46     ` [patch 2/3] Keith's psymtabs fix " Jan Kratochvil

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=20110317124128.GX31264@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=keiths@redhat.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