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] Constify not_just_help_class_command
Date: Wed, 27 Sep 2017 17:17:00 -0000	[thread overview]
Message-ID: <eb7c454d737322be2d810e1a5a2dc7b88fd636e6@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT eb7c454d737322be2d810e1a5a2dc7b88fd636e6 ***

Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: eb7c454d737322be2d810e1a5a2dc7b88fd636e6

Constify not_just_help_class_command

gdb/ChangeLog
2017-09-27  Tom Tromey  <tom@tromey.com>

	* command.h (not_just_help_class_command): Update.
	* cli/cli-decode.h (not_just_help_class_command): Update.
	* cli/cli-decode.c (not_just_help_class_command): Constify.


             reply	other threads:[~2017-09-27 17:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 17:17 sergiodj+buildbot [this message]
2017-09-27 17:20 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-09-27 17:42 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-09-27 18:02 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-09-27 18:06 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-09-27 18:12 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-09-27 18:18 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-09-27 18:35 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-09-27 18:45 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-09-27 19:35 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-09-27 19:59 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " 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=eb7c454d737322be2d810e1a5a2dc7b88fd636e6@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).