From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] thread apply help
Date: Sun, 13 Nov 2005 19:03:00 -0000 [thread overview]
Message-ID: <20051113184040.GF3599@nevyn.them.org> (raw)
In-Reply-To: <43723A70.9050309@st.com>
On Wed, Nov 09, 2005 at 06:05:36PM +0000, Andrew STUBBS wrote:
> Hi,
>
> This patch might qualify as obvious, but I'm not sure what the rules are
> on who's allowed to do that, so here it is.
Anyone who can commit a patch. See MAINTAINERS for the description of
this.
> 2005-11-09 Andrew Stubbs <andrew.stubbs@st.com>
>
> * thread.c (_initialize_thread): Correct the 'thread apply' help
> message.
Yes, this is fine. It'd be nice if the CLI code handled this
automatically, but obviously it doesn't, so...
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-13 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 20:31 Andrew STUBBS
2005-11-13 19:03 ` Daniel Jacobowitz [this message]
2005-11-14 22:18 ` Andrew STUBBS
2005-11-15 4:03 ` Daniel Jacobowitz
2005-11-14 22:42 ` Andrew STUBBS
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=20051113184040.GF3599@nevyn.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.com \
--cc=gdb-patches@sources.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