From: Simon Marchi <simon.marchi@polymtl.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, palves@redhat.com
Subject: Re: [PATCH] Fix MI output for multi-location breakpoints
Date: Mon, 14 Jan 2019 21:05:00 -0000 [thread overview]
Message-ID: <d5515d2c922deec4280db5b940a3a523@polymtl.ca> (raw)
In-Reply-To: <83o98kec4w.fsf@gnu.org>
On 2019-01-13 11:49, Eli Zaretskii wrote:
>> > Which is the third place? I thought we have it only in two places.
>> > The detailed table could come instead of that second place we have
>> > now, not in addition to it. But let's wait with that decision until
>> > we actually see the proposed change for that table.
>>
>> 1. In "@node Mode Options"
>> 2. In "@node Interpreters"
>> 3. In the hypothetical table of MI versions.
>
> We don't need to consider hypothetical issues. When it becomes real,
> we can discuss whether it will replace what's currently in
> "Interpreters" or be an addition.
I have sent a patch for this:
https://sourceware.org/ml/gdb-patches/2019-01/msg00335.html
Simon
next prev parent reply other threads:[~2019-01-14 21:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 0:15 Simon Marchi
2019-01-11 8:04 ` Eli Zaretskii
2019-01-11 20:21 ` Simon Marchi
[not found] ` <83y37qgail.fsf@gnu.org>
2019-01-12 17:01 ` Tom Tromey
2019-01-13 5:09 ` Simon Marchi
2019-01-13 15:32 ` Eli Zaretskii
2019-01-13 16:17 ` Simon Marchi
2019-01-13 16:49 ` Eli Zaretskii
2019-01-14 21:05 ` Simon Marchi [this message]
2019-01-11 12:34 ` Andrew Burgess
2019-01-11 18:39 ` Pedro Alves
2019-01-11 23:36 ` Simon Marchi
2019-01-12 1:40 ` Andrew Burgess
2019-01-12 16:54 ` Tom Tromey
2019-01-13 5:49 ` Simon Marchi
2019-01-11 21:07 ` Simon Marchi
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=d5515d2c922deec4280db5b940a3a523@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=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