Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	 GDB <gdb-patches@sourceware.org>
Subject: Re: Oh dear. I regret to inform you that commit b1308d2c3749cc454f00b70768ee33724d919527 might be unfortunate
Date: Fri, 08 Sep 2017 05:41:00 -0000	[thread overview]
Message-ID: <87o9qlrblf.fsf@redhat.com> (raw)
In-Reply-To: <CAMe9rOrw91SAnAUmtYfKwZCtr1+_ZQz6Yq4NY1E5jn82Jar2mw@mail.gmail.com>	(H. J. Lu's message of "Thu, 7 Sep 2017 19:09:54 -0700")

On Thursday, September 07 2017, H. J. Lu wrote:

> On Thu, Sep 7, 2017 at 4:34 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>>> This bot is next to useless.  I just ignore it.
>>>
>>> This bot shouldn't spam people when the new commit doesn't change
>>> the old error.
>>
>> Personally, I think it is great that we have a buildbot that tests
>> so many configurations and platforms. This is a great tool and
>> while there are issues today, I really don't think we should be
>> ignoring them. The right thing to do was to report/ask here, which
>> led to Sergio immediately jumping on it.  Thank you Sergio!
>>
>> This buildbot is really there to help us out discover regressions
>> soon after we commit, when it's easier to investigate and adjust,
>> or revert if necessary. While we get annoyed sometime, it's still
>> going to benefit us all. Let's encourage its improvement, and offer
>> our help to its development team, rather than denigrate it.
>
> Sure.
>
> FWIW, I got another 5 bogus messsages from:
>
> https://sourceware.org/ml/binutils/2017-09/msg00070.html
>
> which has nothing to do with GDB build failure.  I will put it in
> my spam filter if it doesn't stop.

I'm sorry to hear that.  Things should be more stable now.  Please let
me know if you still receive wrong e-mails.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2017-09-08  5:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1dq0Uz-00056v-Ti@kwanyin.sergiodj.net>
2017-09-07 17:56 ` Palmer Dabbelt
2017-09-07 18:00   ` H.J. Lu
2017-09-07 18:57     ` Sergio Durigan Junior
2017-09-07 19:32       ` H.J. Lu
2017-09-07 19:41         ` Sergio Durigan Junior
2017-09-07 19:52           ` H.J. Lu
2017-09-07 19:54             ` Sergio Durigan Junior
2017-09-07 19:57             ` Sergio Durigan Junior
2017-09-07 23:35     ` Joel Brobecker
2017-09-08  2:10       ` H.J. Lu
2017-09-08  5:41         ` Sergio Durigan Junior [this message]
2017-09-07 18:52   ` Sergio Durigan Junior
2017-09-10  5:54     ` 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=87o9qlrblf.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=palmer@dabbelt.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