From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: $thread convenience variable
Date: Fri, 03 Feb 2006 15:14:00 -0000 [thread overview]
Message-ID: <uy80swk3s.fsf@gnu.org> (raw)
In-Reply-To: <200602031459.40118.ghost@cs.msu.su> (message from Vladimir Prus on Fri, 3 Feb 2006 14:59:39 +0300)
> From: Vladimir Prus <ghost@cs.msu.su>
> Date: Fri, 3 Feb 2006 14:59:39 +0300
> Cc: gdb@sources.redhat.com
>
> > Thanks, but please add its documentation to the GDB manual.
>
> Sure, but I'm more concerned about correctness of the patch (especially pid
> vs. tid), so would rather hear comments on that before doing anything with
> the manual.
What I meant to say was that a code patch without an appropriate docs
patch is incomplete. And we'd rather see complete patches for each
change.
Anyway, a patch for the manual is orthogonal to code changes, in this
case. Whatever patch for the code you will eventually check in, the
description of this feature in the manual will not change, since you
only add a convenience variable. So there's no reason to wait for
comments on the code patch before writing a patch for the manual.
next prev parent reply other threads:[~2006-02-03 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 20:19 Vladimir Prus
2006-02-03 10:58 ` Eli Zaretskii
2006-02-03 11:10 ` Vladimir Prus
2006-02-03 11:28 ` Eli Zaretskii
2006-02-03 11:59 ` Vladimir Prus
2006-02-03 15:14 ` Eli Zaretskii [this message]
2006-02-03 13:04 ` Andrew STUBBS
2006-02-03 13:10 ` Vladimir Prus
2006-02-03 13:56 ` Andrew STUBBS
2006-02-06 23:52 ` Daniel Jacobowitz
2006-02-06 23:49 ` Daniel Jacobowitz
2006-02-07 10:59 ` Andrew STUBBS
2006-02-07 19:31 ` Daniel Jacobowitz
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=uy80swk3s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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