From: Glenn Morris <rgm@gnu.org>
To: 10597-done@debbugs.gnu.org
Subject: bug#10597: [PATCH] GUD-MI's disassembly buffer should follow $PC in the absence of debug information.
Date: Tue, 13 Mar 2012 03:10:29 -0400 [thread overview]
Message-ID: <6p1uoxkmca.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <1327474395.11160.4.camel@garuda3.sysenter> (Kaushik Srenevasan's message of "Tue, 24 Jan 2012 22:53:15 -0800")
Version: 24.0.95
Thanks; applied.
It would be great if you could also suggest ChangeLog entries for any
future changes.
Also, we'll need a copyright assignment to accept any further changes of
more than a few lines total from you. It's a straightforward procedure.
Let me know off-list if you want to, and I can send you the form.
prev parent reply other threads:[~2012-03-13 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 6:53 bug#10597: [PATCH] GUD-MI's disassembly buffer should follow $PC in the absence of debug information Kaushik Srenevasan
2012-03-13 7:10 ` Glenn Morris [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6p1uoxkmca.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=10597-done@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).