From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc: bump 6.x series to 6.2.0
Date: Mon, 22 Aug 2016 23:15:35 +0200 [thread overview]
Message-ID: <877fb8o688.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1471896123-31759-1-git-send-email-gustavo@zacarias.com.ar> (Gustavo Zacarias's message of "Mon, 22 Aug 2016 17:02:03 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
> Adjust some patches to avoid patching the ChangeLog which isn't quite
> the same.
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Is this against next? It doesn't apply for me:
Applying: gcc: bump 6.x series to 6.2.0
Using index info to reconstruct a base tree...
A package/gcc/6.1.0/892-libgcc-mkmap-symver-support-skip_underscore.patch
A package/gcc/6.1.0/893-libgcc-config-bfin-use-the-generic-linker-version-in.patch
A package/gcc/6.1.0/894-libgcc-fix-DWARF-compilation-with-FDPIC-targets.patch
M package/gcc/Config.in.host
M package/gcc/gcc.hash
Falling back to patching base and 3-way merge...
Auto-merging package/gcc/gcc.hash
Auto-merging package/gcc/Config.in.host
CONFLICT (content): Merge conflict in package/gcc/Config.in.host
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-08-22 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 20:02 [Buildroot] [PATCH] gcc: bump 6.x series to 6.2.0 Gustavo Zacarias
2016-08-22 21:15 ` Peter Korsgaard [this message]
2016-08-22 21:52 ` Thomas Petazzoni
2016-08-22 21:56 ` Peter Korsgaard
2016-08-22 22:14 ` Thomas Petazzoni
2016-08-23 10:41 ` Gustavo Zacarias
2016-08-26 14:15 ` Thomas Petazzoni
2016-08-26 14:17 ` Gustavo Zacarias
-- strict thread matches above, loose matches on Subject: below --
2016-09-06 1:12 Gustavo Zacarias
2016-09-07 8:33 ` 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=877fb8o688.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