Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Walfred Tedeschi <walfred.tedeschi@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	       Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: [obv. PATCH 1/1] Fix build breakage
Date: Tue, 09 Feb 2016 14:12:00 -0000	[thread overview]
Message-ID: <56B9F3A8.3050707@redhat.com> (raw)
In-Reply-To: <56B9EE8C.6070805@intel.com>

On 02/09/2016 01:50 PM, Walfred Tedeschi wrote:

> I did not get any e-mail from buildbot till now, i am subscribing for 
> the gdb-testers list so i can keep informed anyway.

Odd.  You should have gotten one by now, as the build slave as already
failed building the reversion commit, and it succeeded the build in
the commit before that one:

 http://gdb-build.sergiodj.net/builders/Fedora-x86_64-cxx-build-m64/builds/1898
 http://gdb-build.sergiodj.net/builders/Fedora-x86_64-cxx-build-m64/builds/1897

Any chance the email is in some spam folder in your mail client?

Sergio, is there any way to check if the email was sent from the buildbot side?

Thanks,
Pedro Alves


  reply	other threads:[~2016-02-09 14:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1455013458-14340-1-git-send-email-walfred.tedeschi@intel.com>
2016-02-09 10:31 ` Pedro Alves
2016-02-09 10:37   ` Tedeschi, Walfred
2016-02-09 10:50     ` Pedro Alves
2016-02-09 10:55       ` Pedro Alves
     [not found]       ` <AC542571535E904D8E8ADAE745D60B19445370CE@IRSMSX104.ger.corp.intel.com>
2016-02-09 11:05         ` Walfred Tedeschi
2016-02-09 11:13           ` Pedro Alves
2016-02-09 13:50             ` Walfred Tedeschi
2016-02-09 14:12               ` Pedro Alves [this message]
2016-02-09 15:36                 ` Walfred Tedeschi
2016-02-09 18:24                 ` Sergio Durigan Junior
2016-02-10 17:02                   ` Tedeschi, Walfred

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=56B9F3A8.3050707@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@redhat.com \
    --cc=walfred.tedeschi@intel.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