[Buildroot] [PATCH V2] gdb: allow building on AArch64 systems

["Alex Bennée" <alex.bennee@linaro.org>]

Thomas Petazzoni writes:

> Dear Alex Benn?e,
>
> On Thu, 07 Aug 2014 10:46:47 +0100, Alex Benn?e wrote:
>
>> > On Wed,  6 Aug 2014 09:42:14 +0100, Alex Benn?e wrote:
>> >> gdb has had AArch64 support since 7.6 which is now the default minimum
>> >> version of GDB in the tree. Older versions are now legacy.
>> >> 
>> >> Signed-off-by: Alex Benn?e <alex.bennee@linaro.org>
>> >
>> > Applied, thanks!
>> 
>> How are you applying the patches? I'm curious because while my local
>> patch shows up in the log with:
>> 
>> commit 0b729ce2baa9903e7d3520196f9fff16cdff24fa
>> Author: Alex Benn?e <alex.bennee@linaro.org>
>> 
>> The one in upstream is:
>> 
>> commit 4372449a4f8e16f763c7d5a0c125ca015a7cbef6
>> Author: alex.bennee at linaro.org <alex.bennee@linaro.org>
>> 
>> I'd usually assume utf-8 shenanigans tripping something up but I see the
>> repo does have names with more accents than mine ;-)
>
> We're using pwclient, which downloads the patch from patchwork and
> applies it with "git am".
>
> There's basically no chance for your local commit used to generate the
> patch to have the same SHA1 as the commit integrated in the official
> repository.

Sorry I was actually talking about the mangled Author field. The SHAs
were just for reference. It looks like it gets mangled as it goes into
patchwork. Compare:

From: =?UTF-8?q?Alex=20Benn=C3=A9e?= <alex.bennee@linaro.org>
To: buildroot at busybox.net
Cc: =?UTF-8?q?Alex=20Benn=C3=A9e?= <alex.bennee@linaro.org>
Subject: [PATCH V2] gdb: allow building on AArch64 systems
Date: Wed,  6 Aug 2014 09:42:14 +0100
Message-Id: <1407314534-5536-1-git-send-email-alex.bennee@linaro.org>

to

Subject: [V2] gdb: allow building on AArch64 systems
From: alex.bennee@linaro.org
X-Patchwork-Id: 376942
Message-Id: <1407314534-5536-1-git-send-email-alex.bennee@linaro.org>
To: buildroot at busybox.net
Date: Wed,  6 Aug 2014 09:42:14 +0100



-- 
Alex Benn?e