From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit 23c4651c060c123493de004ef61d8ed052d46113 might be unfortunate
Date: Mon, 10 Sep 2018 14:08:00 -0000 [thread overview]
Message-ID: <87in3dtpik.fsf@tromey.com> (raw)
In-Reply-To: <83in3dpzed.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 10 Sep 2018 10:47:22 +0300")
Eli> It is clear from the build log that the breakage has nothing to do
Eli> with the change I committed. In particular, the offending parts of
Eli> gnulib's glob.c were not modified by my commit, but by Sergio's commit
Eli> 7a6dbc2 of 2 weeks ago. Why is this being flagged only now?
I think it complains on each commit. Sergio was out last week IIRC and
then there was the Cauldron, so the fix for this is lagging a little.
But I think it should come soon.
Tom
next prev parent reply other threads:[~2018-09-10 14:08 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 ` Oh dear. I regret to inform you that commit 23c4651c060c123493de004ef61d8ed052d46113 might be unfortunate Eli Zaretskii
2018-09-10 14:08 ` Tom Tromey [this message]
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=87in3dtpik.fsf@tromey.com \
--to=tom@tromey.com \
--cc=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