From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: palves@redhat.com, luis_gustavo@mentor.com, gdb-patches@sourceware.org
Subject: Re: [RFC stub-side break conditions 3/5] GDB-side changes
Date: Fri, 13 Jan 2012 08:08:00 -0000 [thread overview]
Message-ID: <834nw0kqts.fsf@gnu.org> (raw)
In-Reply-To: <m3boq8zjhv.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: "Gustavo\, Luis" <luis_gustavo@mentor.com>, Eli Zaretskii <eliz@gnu.org>,
> gdb-patches@sourceware.org
> Date: Thu, 12 Jan 2012 14:41:32 -0700
>
> >>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>
> >>> I suggest "cond.eval." instead of "condeval". Better yet, how about
> >>> "evaluated by"?
>
> >> Sounds good. I'll make that change.
>
> Pedro> Isn't that only visible by MI? Are spaces valid in MI field names?
>
> Yes, it is only visible to MI.
>
> The MI spec does not rule out spaces AFAICT, but I would rather we stick
> to names similar to those we already use. On this basis, "condeval" is
> better than "cond.eval.".
How about "evaluated-by"?
next prev parent reply other threads:[~2012-01-13 7:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 14:56 Luis Machado
2012-01-06 8:47 ` Eli Zaretskii
2012-01-06 22:38 ` Luis Machado
2012-01-07 7:54 ` Eli Zaretskii
2012-01-12 19:44 ` Pedro Alves
2012-01-12 22:20 ` Tom Tromey
2012-01-13 8:08 ` Eli Zaretskii [this message]
2012-01-13 14:33 ` Tom Tromey
2012-01-13 14:44 ` Pedro Alves
2012-01-06 16:23 ` Pedro Alves
2012-01-10 11:14 ` Luis Machado
2012-01-12 19:31 ` Pedro Alves
2012-01-06 21:44 ` Tom Tromey
2012-01-10 14:51 ` Luis Machado
2012-01-13 15:36 ` Yao Qi
2012-01-13 18:13 ` Pedro Alves
2012-01-14 0:42 ` Yao Qi
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=834nw0kqts.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luis_gustavo@mentor.com \
--cc=palves@redhat.com \
--cc=tromey@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