From: gdb-buildbot@sergiodj.net
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Oh dear. I regret to inform you that commit e05550d7a409a0637d87bef377e5d4b9a4b379ac might be unfortunate
Date: Tue, 03 Oct 2017 14:02:00 -0000 [thread overview]
Message-ID: <e05550d7a409a0637d87bef377e5d4b9a4b379ac-master-breakage@gdb-build> (raw)
My lords, ladies, gentlemen, members of the public.
It is a matter of great regret and sadness to inform you that commit:
Use std::string in utils.c
e05550d7a409a0637d87bef377e5d4b9a4b379ac
might have made GDB unwell. Since I am just your Butler BuildBot,
I kindly ask that a human superior officer double-check this.
Please note that if you are reading this message on gdb-patches, there might
be other builders broken.
You can find more details about the unfortunate breakage in the next messages.
Cheers,
Your GDB BuildBot.
reply other threads:[~2017-10-03 14:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e05550d7a409a0637d87bef377e5d4b9a4b379ac-master-breakage@gdb-build \
--to=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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