From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doc] Add section on interrupts to remote protocol documentation
Date: Sat, 19 Nov 2005 01:21:00 -0000 [thread overview]
Message-ID: <20051118151825.1a5550c9@ironwood.lan> (raw)
In-Reply-To: <20051118143309.73c45545@ironwood.lan>
On Fri, 18 Nov 2005 14:33:09 -0700
Kevin Buettner <kevinb@redhat.com> wrote:
> * gdb.texinfo (set remotebreak): Add anchor.
> (X packet): Likewise.
> (Remote Protocol): Add new section `Interrupts' and new index
> entry `interrupts (remote protocol)'.
Committed.
Thanks to everyone who provided feedback on this patch.
Kevin
prev parent reply other threads:[~2005-11-18 22:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 5:59 Kevin Buettner
2005-11-18 8:35 ` Jim Blandy
2005-11-18 11:20 ` Steven Johnson
2005-11-18 11:57 ` Jim Blandy
2005-11-18 17:23 ` Kevin Buettner
2005-11-18 20:25 ` Jim Blandy
2005-11-18 13:53 ` Eli Zaretskii
2005-11-18 15:33 ` Steven Johnson
2005-11-18 14:06 ` Eli Zaretskii
2005-11-18 21:45 ` Kevin Buettner
2005-11-18 21:47 ` Daniel Jacobowitz
2005-11-18 22:07 ` Jim Blandy
2005-11-19 10:57 ` Steven Johnson
2005-11-18 22:18 ` Kevin Buettner
2005-11-18 22:19 ` Michael Snyder
2005-11-18 22:38 ` Eli Zaretskii
2005-11-19 1:21 ` Kevin Buettner [this message]
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=20051118151825.1a5550c9@ironwood.lan \
--to=kevinb@redhat.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