From: Doug Evans <xdje42@gmail.com>
To: Keith Seitz <keiths@redhat.com>
Cc: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [RFA 2/9] Explicit locations v2 - Event locations API
Date: Fri, 06 Jun 2014 06:09:00 -0000 [thread overview]
Message-ID: <CAP9bCMQFodziiLXi-J-mKOdNr3pTJCBTsZS9MYq9EhoKKva_9A@mail.gmail.com> (raw)
In-Reply-To: <m3vbsebnhq.fsf@sspiff.org>
On Thu, Jun 5, 2014 at 10:44 PM, Doug Evans <xdje42@gmail.com> wrote:
> Plus in this case the use of EVENT_LOCATION_LINESPEC as an enum
> value and as a macro name would go away, and we can keep
> EVENT_LOCATION_LINESPEC as the enum value. 1/2 :-)
btw, keeping the enum value spelling as EVENT_LOCATION_LINESPEC
instead of LOCATION_LINESPEC is just a suggestion at this point.
Don't rush out and rename things back.
next prev parent reply other threads:[~2014-06-06 6:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 17:59 Keith Seitz
2014-05-12 22:59 ` Doug Evans
2014-05-30 18:16 ` Keith Seitz
2014-06-06 5:45 ` Doug Evans
2014-06-06 6:09 ` Doug Evans [this message]
2014-09-03 19:32 ` Keith Seitz
2014-10-12 21:40 ` Doug Evans
2015-01-27 4:38 ` Keith Seitz
2015-01-28 20:59 ` Doug Evans
2015-01-28 22:12 ` Doug Evans
2015-01-29 0:04 ` Doug Evans
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=CAP9bCMQFodziiLXi-J-mKOdNr3pTJCBTsZS9MYq9EhoKKva_9A@mail.gmail.com \
--to=xdje42@gmail.com \
--cc=gdb-patches@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).