From: Eli Zaretskii <eliz@gnu.org>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches@sourceware.org, tromey@redhat.com,
msnyder@vmware.com, andre.poenitz@nokia.com, gdb@sourceware.org,
brobecker@adacore.com
Subject: Re: [patch] Remove unimplemented MI commands [Re: Learn function name by its address]
Date: Sun, 28 Jun 2009 03:18:00 -0000 [thread overview]
Message-ID: <83ocs93v20.fsf@gnu.org> (raw)
In-Reply-To: <8ac60eac0906271350o544d5f73i646caa1d29eb24a0@mail.gmail.com>
> Date: Sat, 27 Jun 2009 13:50:30 -0700
> From: Paul Pluzhnikov <ppluzhnikov@google.com>
> Cc: gdb-patches@sourceware.org, tromey@redhat.com, msnyder@vmware.com,
> andre.poenitz@nokia.com, gdb@sourceware.org, brobecker@adacore.com
>
> On Sat, Jun 27, 2009 at 1:43 PM, Eli Zaretskii<eliz@gnu.org> wrote:
>
> > Sorry, no (for this part). Â I asked to leave the text there, just
> > commented away with @ignore..@end ignore.
>
> Shouldn't we be consistent?
> If this constitutes "unwanted clutter" in the code, surely it also
> does in the docs?
I thought the suggestion was to comment it out in the code as well.
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.
next prev parent reply other threads:[~2009-06-28 3:18 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 [this message]
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
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=83ocs93v20.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andre.poenitz@nokia.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=ppluzhnikov@google.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