From: Stan Shebs <stan@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [multiprocess] RFA: fix menu in documentation
Date: Sat, 22 Nov 2008 05:06:00 -0000 [thread overview]
Message-ID: <4926F9CD.5000006@codesourcery.com> (raw)
In-Reply-To: <m3ljvdc9qj.fsf@fleche.redhat.com>
Tom Tromey wrote:
>>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
>>>>>>
>
> Tom> +* Inferiors:: Debugging Multiple Inferiors
> Tom> * Multiple Programs:: Debugging multiple programs
>
> Pedro pointed out the goofy capitalization here -- I had just copied
> the @section and not noticed this. Here's a better patch.
>
This is fine, thanks! Feel free to make obvious fixes on the branch, as
long as they are to the changed bits, otherwise it's kind of pointless. :-)
Stan
next prev parent reply other threads:[~2008-11-21 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 22:37 Tom Tromey
2008-11-21 22:54 ` Tom Tromey
2008-11-22 5:06 ` Stan Shebs [this message]
2008-11-22 16:40 ` Tom Tromey
2008-11-22 5:29 ` Eli Zaretskii
2008-11-22 5:12 ` Eli Zaretskii
2008-11-22 16:39 ` Tom Tromey
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=4926F9CD.5000006@codesourcery.com \
--to=stan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--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