From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: time to create the GDB 8.1.x branch?
Date: Mon, 27 Nov 2017 22:20:00 -0000 [thread overview]
Message-ID: <20171127222011.tyga6cjdd2d52dlj@adacore.com> (raw)
In-Reply-To: <9b725473-9732-ff68-f0f2-b8a702d81c81@redhat.com>
Hi Pedro,
> The remaining part is the support for wild matching (ignore
> leading classes/namespaces) for C++, and support for breakpoints on
> symbols with ABI tags.
> Keith reviewed the whole series but I haven't gotten around to
> addressing his comments on that part of the series yes (since
> only recently that lookup_name_info patch got in). I'll try
> to do that ASAP.
I am trying to update the release's wiki page, by listing all
the pending changes, and provide links to discussions and patches.
Is that the patch series you'd like to get in?
https://www.sourceware.org/ml/gdb-patches/2017-11/msg00689.html
Thanks!
--
Joel
next prev parent reply other threads:[~2017-11-27 22:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 19:15 Joel Brobecker
2017-11-21 10:50 ` Ulrich Weigand
2017-11-27 21:55 ` Joel Brobecker
2017-11-28 19:44 ` Ulrich Weigand
2017-11-28 20:32 ` Pedro Alves
2017-11-29 13:20 ` Pedro Alves
2017-11-29 21:00 ` Joel Brobecker
2017-11-29 21:49 ` Pedro Alves
2017-11-29 22:20 ` Joel Brobecker
2017-11-21 11:10 ` Yao Qi
2017-11-21 12:39 ` Pedro Alves
2017-11-27 22:20 ` Joel Brobecker [this message]
2017-11-27 22:41 ` Pedro Alves
2017-11-29 20:56 ` Joel Brobecker
2017-11-29 22:20 ` Pedro Alves
2017-11-29 22:46 ` Joel Brobecker
2017-11-22 13:07 ` Yao Qi
2017-11-27 22:06 ` Joel Brobecker
2017-11-27 22:14 ` Joel Brobecker
2017-11-28 12:38 ` Yao Qi
2017-11-29 20:58 ` Joel Brobecker
2017-11-22 18:03 ` Sergio Durigan Junior
2017-11-27 22:23 ` Joel Brobecker
2017-11-28 17:08 ` Sergio Durigan Junior
2017-11-23 15:16 ` Pedro Alves
2017-11-23 16:50 ` Joel Brobecker
2017-11-23 17:32 ` Pedro Alves
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=20171127222011.tyga6cjdd2d52dlj@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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