From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: Alan Modra <amodra@gmail.com>
Cc: gdb-patches@sourceware.org, Mark Wielaard <mark@klomp.org>
Subject: Re: Your commit 'Create sdynrelro for elfn32 mips too' broke GDB
Date: Sat, 14 Jan 2017 17:58:00 -0000 [thread overview]
Message-ID: <87r345frqu.fsf@sergiodj.net> (raw)
In-Reply-To: <20170114081809.GW32333@bubble.grove.modra.org> (Alan Modra's message of "Sat, 14 Jan 2017 18:48:09 +1030")
On Saturday, January 14 2017, Alan Modra wrote:
> On Fri, Jan 13, 2017 at 08:38:02PM -0500, sergiodj+buildbot@sergiodj.net wrote:
>> Hello there,
>>
>> Your commit:
>>
>> Create sdynrelro for elfn32 mips too
>> b7aba156196caf59117741eae5e93b578d0b59f4
>>
>> broke GDB. Please fix it, or the GDB gods will get you.
>
> Please fix your buildbot. Don't expect me to reply to the next
> report. I'm ignoring it.
Sorry about the noise.
Fixing this has proven harder than I thought. I decided to temporarily
disable the e-mail notifications for the builders associated with both
wildebeest-* slaves (managed by Mark), because they are the ones having
timeout problems when linking GDB.
Hey Mark, would it be possible for you to take a look at this issue?
Thanks in advance!
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2017-01-14 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1cSDIA-0000DC-9f@kwanyin.sergiodj.net>
2017-01-14 8:18 ` Alan Modra
2017-01-14 17:58 ` Sergio Durigan Junior [this message]
2017-01-14 18:22 ` Mark Wielaard
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=87r345frqu.fsf@sergiodj.net \
--to=sergiodj@sergiodj.net \
--cc=amodra@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.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