From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Cross <scross@undo-software.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: Always run GDB command post-hook after pre-hook has been run
Date: Wed, 24 Feb 2016 18:01:00 -0000 [thread overview]
Message-ID: <83lh6agf8o.fsf@gnu.org> (raw)
In-Reply-To: <CA+gYvwe81AEyckmYCsqGaxpr9EQ7K6e6XFjyOFDd++mX+k0iFA@mail.gmail.com> (message from Stephen Cross on Wed, 24 Feb 2016 14:46:05 +0000)
> Date: Wed, 24 Feb 2016 14:46:05 +0000
> From: Stephen Cross <scross@undo-software.com>
> Cc: gdb-patches@sourceware.org
>
> Here's a patch that adds 'hookerror-' to GDB. This passes the test suite
> (running 'make check' in the 'gdb' directory).
>
> Do you think this patch is acceptable? Are there any further changes that you'd
> like me to make?
The documentation part is approved, but I don't see the ChangeLog
entry for it and I also think this should be called out in NEWS.
Thanks.
prev parent reply other threads:[~2016-02-24 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 18:17 Stephen Cross
2015-12-02 18:24 ` Stephen Cross
2015-12-03 11:54 ` Pedro Alves
2015-12-03 16:11 ` Stephen Cross
2015-12-09 17:03 ` Pedro Alves
2016-01-13 15:21 ` Stephen Cross
2016-02-24 14:46 ` Stephen Cross
2016-02-24 18:01 ` Eli Zaretskii [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=83lh6agf8o.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=scross@undo-software.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).