From: Pedro Alves <palves@redhat.com>
To: gdb-buildbot@sergiodj.net, gdb-patches@sourceware.org
Subject: [fixed] Re: Oh dear. I regret to inform you that commit e6ed716cd5514c08b9d7c469d185b1aa177dbc22 might be unfortunate
Date: Thu, 13 Jun 2019 08:27:00 -0000 [thread overview]
Message-ID: <d7433d90-2295-907b-6b36-8f515a1d5f8d@redhat.com> (raw)
In-Reply-To: <e6ed716cd5514c08b9d7c469d185b1aa177dbc22-master-breakage@gdb-build>
This was fixed by:
https://sourceware.org/ml/gdb-patches/2019-06/msg00237.html
Thanks,
Pedro Alves
prev parent reply other threads:[~2019-06-13 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 2:42 gdb-buildbot
2019-06-13 2:42 ` Breakage on builder RHEL-s390x-m64, revision e6ed716cd5514c08b9d7c469d185b1aa177dbc22 gdb-buildbot
2019-06-13 3:41 ` Breakage on builder NetBSD-x86_64-m64, " gdb-buildbot
2019-06-13 8:27 ` Pedro Alves [this message]
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=d7433d90-2295-907b-6b36-8f515a1d5f8d@redhat.com \
--to=palves@redhat.com \
--cc=gdb-buildbot@sergiodj.net \
--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