From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] ARC: bump tools to 2014.08 release
Date: Mon, 01 Sep 2014 16:52:23 +0200 [thread overview]
Message-ID: <87bnqzl7fc.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1409554847.16864.7.camel@abrodkin-8560l.internal.synopsys.com> (Alexey Brodkin's message of "Mon, 1 Sep 2014 07:00:48 +0000")
>>>>> "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:
Hi,
>> Well, you can let me do the rebase myself, but it will probably go faster if you
>> do it.
> I've just checked what's the difference between master and next that
> causes problems on patch application.
> And it looks the reason is in "next" there's a commit missing:
---> ---
> gcc/arc-4.8-R3: add patch to enable more C++ features with uClibc
> http://git.buildroot.net/buildroot/commit/package/gcc/arc-4.8-R3?id=4bb2a05e8133f2f553b8e0cd6af53dfa8b8208b1
> https://patchwork.ozlabs.org/patch/379707/
---> ---
> And since this patch
> (package/binutils/arc-4.8-R3/0001-arc-Honor-DESTDIR-in-custom-Makefile.patch) should be moved to "arc-2014.08" (and my current v2 change does it) I'm not sure if there's a reason to do changes to "next" or just wait before "master" is open to new submissions.
> Otherwise we may whether lose history or Thomas' patch.
> Let me know if that's fine for this v2 to be applied later directly on
> "master".
Yes, I will apply v2 now that next has been merged into master. Thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-09-01 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 17:33 [Buildroot] [PATCH v2] ARC: bump tools to 2014.08 release Alexey Brodkin
2014-08-26 14:49 ` Alexey Brodkin
2014-08-26 14:58 ` Thomas Petazzoni
2014-08-26 15:01 ` Alexey Brodkin
2014-08-26 21:50 ` Peter Korsgaard
2014-08-26 21:53 ` Alexey Brodkin
2014-08-26 22:02 ` Peter Korsgaard
2014-08-26 22:04 ` Alexey Brodkin
2014-09-01 7:00 ` Alexey Brodkin
2014-09-01 14:52 ` Peter Korsgaard [this message]
2014-09-01 14:53 ` Peter Korsgaard
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=87bnqzl7fc.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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