public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Rename rl_callback_read_char_wrapper -> gdb_rl_callback_read_char_wrapper
Date: Fri, 22 Apr 2016 16:05:00 -0000 [thread overview]
Message-ID: <3c610247abdf7fd6d22d21f11552d223be1e12cd@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 3c610247abdf7fd6d22d21f11552d223be1e12cd ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3c610247abdf7fd6d22d21f11552d223be1e12cd
Rename rl_callback_read_char_wrapper -> gdb_rl_callback_read_char_wrapper
Use the "gdb_rl_" prefix like other gdb readline function wrappers to
make it clear this is a gdb function, not a readline function.
gdb/ChangeLog:
2016-04-22 Pedro Alves <palves@redhat.com>
* event-top.c (rl_callback_read_char_wrapper): Rename to ...
(gdb_rl_callback_read_char_wrapper): ... this.
(change_line_handler, gdb_setup_readline): Adjust.
next reply other threads:[~2016-04-22 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 16:05 sergiodj+buildbot [this message]
2016-04-22 16:05 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2016-04-22 16:30 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-04-22 17:08 ` Failures on Debian-i686, " sergiodj+buildbot
2016-04-23 4:06 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2016-04-23 5:00 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2016-04-23 5:37 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-04-23 14:39 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-04-23 15:12 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2016-04-26 8:41 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
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=3c610247abdf7fd6d22d21f11552d223be1e12cd@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--cc=gdb-testers@sourceware.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.
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).