From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit 62f29fda90cf1d5a1899f57ef78452471c707fd6 might be unfortunate
Date: Sat, 29 Dec 2018 04:14:00 -0000 [thread overview]
Message-ID: <87imzdm0k6.fsf@tromey.com> (raw)
In-Reply-To: <62f29fda90cf1d5a1899f57ef78452471c707fd6-master-breakage@gdb-build> (gdb-buildbot@sergiodj.net's message of "Fri, 28 Dec 2018 18:23:03 -0500")
>>>>> "gdb-buildbot" == gdb-buildbot <gdb-buildbot@sergiodj.net> writes:
gdb-buildbot> Highlight source code using GNU Source Highlight
gdb-buildbot> 62f29fda90cf1d5a1899f57ef78452471c707fd6
I fixed this.
It's possible that there will be other failures -- while I tested everything
locally (obviously forgetting the no-source-highlight case), one never
can be sure -- and if there are I will fix them tomorrow.
Tom
next prev parent reply other threads:[~2018-12-29 4:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 23:23 gdb-buildbot
2018-12-28 23:23 ` Breakage on builder Solaris11-sparcv9-m64, revision 62f29fda90cf1d5a1899f57ef78452471c707fd6 gdb-buildbot
2018-12-28 23:44 ` Breakage on builder Solaris11-amd64-m64, " gdb-buildbot
2018-12-28 23:52 ` Breakage on builder RHEL-s390x-m64, " gdb-buildbot
2018-12-29 0:20 ` Breakage on builder NetBSD-x86_64-m64, " gdb-buildbot
2018-12-29 4:14 ` Tom Tromey [this message]
2018-12-29 15:46 ` Breakage on builder Debian-s390x-native-extended-gdbserver-m64, " gdb-buildbot
2018-12-29 15:49 ` Breakage on builder Debian-s390x-native-gdbserver-m64, " gdb-buildbot
2018-12-29 15:52 ` Breakage on builder Debian-s390x-m64, " gdb-buildbot
2018-12-29 19:21 ` Breakage on builder Fedora-i686, " gdb-buildbot
2018-12-29 19:27 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2018-12-29 19:31 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2018-12-29 19:33 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2018-12-29 19:39 ` Breakage on builder Fedora-x86_64-w64-mingw32, " gdb-buildbot
2018-12-29 19:40 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2018-12-29 19:40 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2018-12-29 19:45 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2018-12-29 20:05 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2018-12-30 9:34 ` Breakage on builder Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2018-12-30 9:42 ` Breakage on builder Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2018-12-30 9:50 ` Breakage on builder Ubuntu-Aarch64-m64, " gdb-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=87imzdm0k6.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@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