Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-patches@sourceware.org
To: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Oh dear.  I regret to inform you that commit 775e241e9c5f2b2ff2b59972ab70e5f20763fae6 might be unfortunate
Date: Mon, 12 Aug 2019 20:14:00 -0000	[thread overview]
Message-ID: <775e241e9c5f2b2ff2b59972ab70e5f20763fae6-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:

	Import readline 7.0 (patch 5)
	775e241e9c5f2b2ff2b59972ab70e5f20763fae6

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:[~2019-08-12 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-12 20:14 gdb-buildbot [this message]
2019-08-12 20:14 ` Breakage on builder Fedora-x86_64-w64-mingw32, revision 775e241e9c5f2b2ff2b59972ab70e5f20763fae6 gdb-buildbot
2019-08-12 20:35   ` Christian Biesinger via gdb-patches
2019-08-12 20:36     ` Tom Tromey

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=775e241e9c5f2b2ff2b59972ab70e5f20763fae6-master-breakage@gdb-build \
    --to=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