public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: Alan Modra <amodra@gmail.com>, gdb-patches@sourceware.org
Subject: Oh dear. I regret to inform you that commit dce2246a6c934bf35157e8970d0da5a11aefb282 might be unfortunate
Date: Wed, 06 Dec 2017 07:50:00 -0000	[thread overview]
Message-ID: <dce2246a6c934bf35157e8970d0da5a11aefb282-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:

	Comment tidy
	dce2246a6c934bf35157e8970d0da5a11aefb282

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-12-06  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06  7:50 gdb-buildbot [this message]
2017-12-06  7:50 ` Breakage on builder Fedora-s390x-m64, revision dce2246a6c934bf35157e8970d0da5a11aefb282 gdb-buildbot
2017-12-07 16:43   ` 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=dce2246a6c934bf35157e8970d0da5a11aefb282-master-breakage@gdb-build \
    --to=gdb-buildbot@sergiodj.net \
    --cc=amodra@gmail.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).