From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Remove unimplemented MI commands [Re: Learn function name by its address]
Date: Sun, 28 Jun 2009 18:16:00 -0000 [thread overview]
Message-ID: <83ljnc441o.fsf@gnu.org> (raw)
In-Reply-To: <h273bs$glu$1@ger.gmane.org>
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sun, 28 Jun 2009 10:42:04 +0400
>
> > But in any case, no, there's no consistency issue here: while most
> > humans read the code, almost no one reads the Texinfo sources of the
> > docs. People read the manual in its Info, HTML, or PDF formats, where
> > the @ignore'd parts are gone.
>
> But is there any value in keeping those (fairly useless) docs commented out
> in texinfo source? The changes that most of them will be revived is close to
> zero, and reviving will require writing real docs anyway.
You may be right. But keeping them does no harm, while deleting them
when the time comes is easy. Meanwhile, they might serve as design
guidelines if someone needs that. In addition -- and to me this is no
small thing -- they pay respect to the original GDB/MI designers, some
of whom are still among us.
next prev parent reply other threads:[~2009-06-28 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 18:44 Paul Pluzhnikov
2009-06-27 19:03 ` Paul Pluzhnikov
2009-06-27 20:43 ` Eli Zaretskii
2009-06-27 20:50 ` Paul Pluzhnikov
2009-06-28 3:18 ` Eli Zaretskii
2009-06-28 4:13 ` Paul Pluzhnikov
2009-06-28 18:01 ` Eli Zaretskii
2009-06-28 19:32 ` Paul Pluzhnikov
[not found] ` <83ocs93v20.fsf__10960.3112018251$1246159141$gmane$org@gnu.org>
2009-06-28 6:42 ` Vladimir Prus
2009-06-28 18:16 ` Eli Zaretskii [this message]
2009-06-28 6:45 ` Vladimir Prus
2009-07-01 19:14 ` Stan Shebs
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=83ljnc441o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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