From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/2] Sync libiberty with gcc upstream
Date: Wed, 24 Jun 2015 13:52:00 -0000 [thread overview]
Message-ID: <CABOHX+cYeXF4vQ+TAhrwrp=yqLKK2zPbUHLbyxobn-2yyD1_2g@mail.gmail.com> (raw)
In-Reply-To: <558A95CE.2060506@redhat.com>
On 24 June 2015 at 13:34, Pedro Alves <palves@redhat.com> wrote:
> On 06/19/2015 04:18 PM, Iain Buclaw wrote:
>> Belated attempt at downstreaming libiberty changes from upstream.
>> Split it into two patches, one with dlang related changes, the other
>> with everything else.
>>
>> As requested, commits have been replayed ontop of gdb rather than a
>> straight diff between the directories.
>
> Excellent, thanks.
>
> If we regenerate the affected configure files afterwards, do end up
> with no changes? If so, the two patches are OK.
>
If by regenerating, you mean by using autoreconf2.64 on the toplevel
and libiberty directories, then yes no further changes crop up.
> I assume diffing the dirs still comes up empty after these?
>
Diffing the libiberty directory between gcc and gdb comes up empty
after these, yes.
Regards
Iain
next prev parent reply other threads:[~2015-06-24 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 15:18 Iain Buclaw
2015-06-24 11:34 ` Pedro Alves
2015-06-24 13:52 ` Iain Buclaw [this message]
2015-06-24 13:54 ` Pedro Alves
2015-06-25 14:23 ` [BUILDROBOT] asprintf() no longer declared (was: [PATCH v2 1/2] Sync libiberty with gcc upstream) Jan-Benedict Glaw
2015-06-25 21:13 ` [BUILDROBOT] asprintf() no longer declared Sergio Durigan Junior
2015-06-30 16:25 ` [BUILDROBOT] asprintf() no longer declared (was: [PATCH v2 1/2] Sync libiberty with gcc upstream) Jan-Benedict Glaw
2015-06-30 16:42 ` [BUILDROBOT] asprintf() no longer declared Luis Machado
2015-06-30 16:55 ` Pedro Alves
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='CABOHX+cYeXF4vQ+TAhrwrp=yqLKK2zPbUHLbyxobn-2yyD1_2g@mail.gmail.com' \
--to=ibuclaw@gdcproject.org \
--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