Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: jose.marchesi@oracle.com (Jose E. Marchesi)
To: gdb-patches@sourceware.org
Subject: Re: Oh dear. I regret to inform you that commit fd0de36e274c8141a5dd4579cd04856dc88370da might be unfortunate
Date: Thu, 23 May 2019 21:30:00 -0000	[thread overview]
Message-ID: <878suw3lm6.fsf@oracle.com> (raw)
In-Reply-To: <fd0de36e274c8141a5dd4579cd04856dc88370da-master-breakage@gdb-build>	(gdb-buildbot's message of "Thu, 23 May 2019 15:44:06 -0400")


    My lords, ladies, gentlemen, members of the public.
    
    It is a matter of great regret and sadness to inform you that commit:
    
    	bfd: add support for eBPF
    	fd0de36e274c8141a5dd4579cd04856dc88370da
    
    might have made GDB unwell.  Since I am just your Butler BuildBot,
    I kindly ask that a human superior officer double-check this.

Mea culpa!!
http://sourceware.org/ml/binutils/2019-05/msg00328.html should fix this.

Salud! (and sorry!)


      parent reply	other threads:[~2019-05-23 21:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 19:44 gdb-buildbot
2019-05-23 19:44 ` Breakage on builder Fedora-i686, revision fd0de36e274c8141a5dd4579cd04856dc88370da gdb-buildbot
2019-05-23 21:30 ` Jose E. Marchesi [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=878suw3lm6.fsf@oracle.com \
    --to=jose.marchesi@oracle.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