From: Eli Zaretskii <eliz@gnu.org>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit 23c4651c060c123493de004ef61d8ed052d46113 might be unfortunate
Date: Mon, 10 Sep 2018 07:47:00 -0000 [thread overview]
Message-ID: <83in3dpzed.fsf@gnu.org> (raw)
In-Reply-To: <23c4651c060c123493de004ef61d8ed052d46113-master-breakage@gdb-build> (gdb-buildbot@sergiodj.net)
> From: gdb-buildbot@sergiodj.net
> Date: Mon, 10 Sep 2018 03:19:34 -0400
>
> My lords, ladies, gentlemen, members of the public.
>
> It is a matter of great regret and sadness to inform you that commit:
>
> Fix "make install-strip" failure to install gdb-add-index.sh
> 23c4651c060c123493de004ef61d8ed052d46113
>
> might have made GDB unwell. Since I am just your Butler BuildBot,
> I kindly ask that a human superior officer double-check this.
It is clear from the build log that the breakage has nothing to do
with the change I committed. In particular, the offending parts of
gnulib's glob.c were not modified by my commit, but by Sergio's commit
7a6dbc2 of 2 weeks ago. Why is this being flagged only now?
next prev parent reply other threads:[~2018-09-10 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 7:19 gdb-buildbot
2018-09-10 7:19 ` Breakage on builder RHEL-s390x-m64, revision 23c4651c060c123493de004ef61d8ed052d46113 gdb-buildbot
2018-09-10 7:47 ` Eli Zaretskii [this message]
2018-09-10 14:08 ` Oh dear. I regret to inform you that commit 23c4651c060c123493de004ef61d8ed052d46113 might be unfortunate Tom Tromey
2018-09-10 15:29 ` Sergio Durigan Junior
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=83in3dpzed.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.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