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] Bump version number to 2.30.51
Date: Sat, 13 Jan 2018 14:31:00 -0000 [thread overview]
Message-ID: <769c7ea507209948135facd04bf8defc3f21a8a4@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 769c7ea507209948135facd04bf8defc3f21a8a4 ***
Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 769c7ea507209948135facd04bf8defc3f21a8a4
Bump version number to 2.30.51
bfd/
* version.m4: Bump version to 2.30.51
* configure: Regenerate.
binutils/
* configure: Regenerate.
gas/
* configure: Regenerate.
gprof/
* configure: Regenerate.
ld/
* configure: Regenerate.
opcodes/
* configure: Regenerate.
next reply other threads:[~2018-01-13 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 14:31 sergiodj+buildbot [this message]
2018-01-13 14:31 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot
2018-01-13 14:34 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-01-13 14:39 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-01-13 14:51 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-13 15:06 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-01-13 15:08 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-01-13 15:56 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-01-13 22:32 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-13 23:04 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-01-13 23:36 ` Failures on Ubuntu-AArch32-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=769c7ea507209948135facd04bf8defc3f21a8a4@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).