Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/3] Make "break foo" find "A::foo", A::B::foo", etc. [C++ and wild matching]
Date: Mon, 27 Nov 2017 17:47:00 -0000	[thread overview]
Message-ID: <83fu8z62c7.fsf@gnu.org> (raw)
In-Reply-To: <1511802824-643-3-git-send-email-palves@redhat.com> (message from	Pedro Alves on Mon, 27 Nov 2017 17:13:43 +0000)

> From: Pedro Alves <palves@redhat.com>
> Date: Mon, 27 Nov 2017 17:13:43 +0000
> 
>   - Documentation bits were tweaked accordingly, so may benefit from
>     another review.

Reviewed; still OK.

Thanks.


  reply	other threads:[~2017-11-27 17:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 17:13 [PATCH v2 0/3] C++ debugging improvements: wild matching and ABI tags Pedro Alves
2017-11-27 17:13 ` [PATCH v2 3/3] Breakpoints in symbols with ABI tags (PR c++/19436) Pedro Alves
2017-11-28  3:47   ` Keith Seitz
2017-11-27 17:13 ` [PATCH v2 1/3] Handle custom completion match prefix / LCD Pedro Alves
2017-11-28  1:42   ` Keith Seitz
2017-11-27 17:14 ` [PATCH v2 2/3] Make "break foo" find "A::foo", A::B::foo", etc. [C++ and wild matching] Pedro Alves
2017-11-27 17:47   ` Eli Zaretskii [this message]
2017-11-28  0:01   ` Pedro Alves
2017-11-28  0:14     ` [PATCH v2.1 " Pedro Alves
2017-11-28  2:50       ` Keith Seitz
2017-11-28 12:39         ` Pedro Alves
2017-11-28 17:35           ` Keith Seitz
2017-11-29 19:52             ` Pedro Alves
2017-11-27 17:33 ` [PATCH v2 0/3] C++ debugging improvements: wild matching and ABI tags 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=83fu8z62c7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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