From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sources.redhat.com
Cc: nickrob@snap.net.nz
Subject: Re: [PATCH] -stack-select-frame
Date: Fri, 17 Jun 2005 09:55:00 -0000 [thread overview]
Message-ID: <upsul1ceg.fsf@gnu.org> (raw)
In-Reply-To: <20050617032149.GF17013@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 16 Jun 2005 23:21:49 -0400)
> Date: Thu, 16 Jun 2005 23:21:49 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sources.redhat.com
>
> Maybe it is time to mark the unimplemented commands in the manual?
They should generally be excluded from the manual. Feel free to ifdef
them away (using @ignore..@end ignore), with a comment saying that
they are not implemented yet. If you don't have time, I will get to
that eventually. Thanks for drawing my attention to this command; I
must have missed it when I excluded all the other unimplemented MI
commands while integrating gdbmi.texinfo into the manual.
> I'm not real thrilled with doing this; we don't get to decide what
> people do or do not use, so documenting things that people do use as
> unstable does no one any favors. However, I've been hearing a lot of
> convincing points that we have more freedom here than I thought. So
> I'm getting more comfortable with changes.
I, too, prefer stabilizing MI to saying that it's unstable. But if no
one steps forward to do the work, I see nothing wrong in warning users
that a particular GDB area is under construction.
next prev parent reply other threads:[~2005-06-17 9:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 3:36 Nick Roberts
2005-06-16 4:42 ` Daniel Jacobowitz
2005-06-16 6:41 ` Nick Roberts
2005-06-16 13:21 ` Daniel Jacobowitz
2005-06-16 22:58 ` Nick Roberts
2005-06-16 23:20 ` Bob Rossi
2005-06-16 23:47 ` Daniel Jacobowitz
2005-06-17 3:07 ` Nick Roberts
2005-06-17 3:21 ` Daniel Jacobowitz
2005-06-17 7:37 ` Nick Roberts
2005-06-17 10:15 ` Eli Zaretskii
2005-06-17 13:33 ` Daniel Jacobowitz
2005-06-18 8:56 ` Eli Zaretskii
2005-06-17 9:55 ` Eli Zaretskii [this message]
2005-06-17 9:46 ` Eli Zaretskii
2005-06-16 18:23 ` Eli Zaretskii
2005-06-16 20:15 ` Jason Molenda
2005-06-16 23:04 ` Nick Roberts
2005-06-16 23:30 ` Jason Molenda
2005-06-17 7:22 ` Nick Roberts
2005-06-17 13:30 ` Daniel Jacobowitz
2005-06-17 19:48 ` Jason Molenda
2005-06-17 22:35 ` Stan Shebs
2005-06-17 22:59 ` Daniel Jacobowitz
2005-06-17 23:31 ` Nick Roberts
[not found] <1119003319.5434.ezmlm@sources.redhat.com>
2005-06-17 17:45 ` Jim Ingham
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=upsul1ceg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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