From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: brobecker@adacore.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] New annotation for threads
Date: Sat, 17 May 2008 21:18:00 -0000 [thread overview]
Message-ID: <ufxshhwap.fsf@gnu.org> (raw)
In-Reply-To: <18478.48682.13900.951343@kahikatea.snap.net.nz>
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sat, 17 May 2008 23:14:50 +1200
> Cc: brobecker@adacore.com, gdb-patches@sources.redhat.com
>
> Documenting a feature helps and encourages it's use.
Then you should submit a patch to remove all docs of annotations from
the manual, and try to convince us to accept it. Not documenting just
one piece is inconsistent and doesn't make sense.
> For this reason, and because annotations is deprecated, I was
> intending not to document it. Why do you think it should be
> documented?
Because annotations are generally documented, and because they are
still part of GDB. As long as annotations are part of GDB, I will
object to any user-visible change in them that is not documented in
the manual.
next prev parent reply other threads:[~2008-05-17 13:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 16:06 Nick Roberts
2008-04-29 4:47 ` Joel Brobecker
2008-04-29 14:19 ` Nick Roberts
2008-05-01 18:18 ` Joel Brobecker
2008-05-01 18:44 ` Daniel Jacobowitz
2008-05-01 23:31 ` Nick Roberts
2008-05-01 23:37 ` Joel Brobecker
2008-05-02 0:07 ` Nick Roberts
2008-05-02 5:50 ` Joel Brobecker
2008-05-02 10:41 ` Eli Zaretskii
2008-05-17 15:51 ` Nick Roberts
2008-05-17 19:15 ` Stan Shebs
2008-05-17 21:18 ` Eli Zaretskii [this message]
2008-05-18 3:20 ` Bob Rossi
2008-05-18 9:11 ` Bob Rossi
2008-05-18 17:44 ` Eli Zaretskii
2008-05-19 8:48 ` Joel Brobecker
2008-05-19 9:09 ` Nick Roberts
2008-05-19 9:44 ` Eli Zaretskii
2008-05-19 12:39 ` Nick Roberts
2008-05-19 13:23 ` Eli Zaretskii
2008-05-20 15:27 ` Joel Brobecker
2008-05-20 16:10 ` Nick Roberts
2008-05-20 16:43 ` Nick Roberts
2008-05-20 18:09 ` Joel Brobecker
2008-05-21 3:55 ` Nick Roberts
2008-05-21 7:22 ` Joel Brobecker
2008-05-20 22:21 ` Eli Zaretskii
2008-05-20 22:54 ` Joel Brobecker
2008-05-21 3:26 ` Eli Zaretskii
2008-05-21 9:33 ` Joel Brobecker
2008-05-21 15:11 ` Nick Roberts
2008-05-21 15:14 ` Joel Brobecker
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=ufxshhwap.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--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