From: Walfred Tedeschi <walfred.tedeschi@intel.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [obv. PATCH 1/1] Fix build breakage
Date: Tue, 09 Feb 2016 11:05:00 -0000 [thread overview]
Message-ID: <56B9C7FF.3020203@intel.com> (raw)
In-Reply-To: <AC542571535E904D8E8ADAE745D60B19445370CE@IRSMSX104.ger.corp.intel.com>
Am 2/9/2016 um 11:55 AM schrieb :
>
>
> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Tuesday, February 09, 2016 11:50 AM
> To: Tedeschi, Walfred
> Cc: gdb-patches@sourceware.org
> Subject: Re: [obv. PATCH 1/1] Fix build breakage
>
> On 02/09/2016 10:37 AM, Tedeschi, Walfred wrote:
>> From: gdb-patches-owner@sourceware.org
>> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Pedro Alves
>
>> How is this better than what Simon proposed?
>
>> I haven't seem Simon's proposal, have just feel sorry to have caused this breakage, and tried to fix.
>> Just noticed that with the e-mail from Sergio this early morning.
>
> Simon's fix was quoted in Sergio's e-mail. :-)
>
>> I will revert what I just pushed,
>
> You reverted one patch unrelated patch too:
>
> commit 0635c8759326e9431604b3359185cbf96740521d
> Author: Walfred Tedeschi <walfred.tedeschi@intel.com>
>
> Revert "Add a more helpful warning message to explain why some AArch64 relocations can overflow."
>
> This reverts commit 2ea53e003163338a403d5afbb2046cafb8f3abe9.
>
> I've reapplied 2ea53e003163 now, preserving the original author (for "git blame").
>
>
> BTW, given you first fixed the C++ build, and then broke it again with the revert, you should have gotten another e-mail from the buildbot about C++ build breakage. Can you confirm whether you got one this time?
>
> Thanks,
> Pedro Alves
>
> Pedro,
>
> I did not get the e-mail fro build bot again. :(
>
>
Pedro and All,
Sergio's email to me did not noted that, only the one reporting the
status of the branching. I saw about the same time i saw your e-mail.
See below:
https://sourceware.org/ml/gdb-patches/2016-02/msg00209.html
I will keep an eye on and inform you at end of the day. But looks like i
do not get more e-mails from build bot. :|
Is there a web-page that you can follow the builds for a specific commit?
Sorry again for the inconvenience,
-Fred
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2016-02-09 11:05 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 [this message]
2016-02-09 11:13 ` Pedro Alves
2016-02-09 13:50 ` Walfred Tedeschi
2016-02-09 14:12 ` Pedro Alves
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=56B9C7FF.3020203@intel.com \
--to=walfred.tedeschi@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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