From: "Peter A. Bigot" <pab@pabigot.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: reconciling pending gcc recipe updates
Date: Thu, 14 Aug 2014 03:47:30 -0500 [thread overview]
Message-ID: <53EC77A2.9040809@pabigot.com> (raw)
Khem and I both have pending patches to recipes-devtools/gcc. A problem
is that the first one of mine is a whitespace cleanup, and I don't think
his are based on that.
What can be done to effectively reconcile any conflicts between these?
I'd really prefer to keep the cleanup patch, so I'd be happy to
cherry-pick Khem's changes into my series. I'm not sure if his "Looks
good" follow-ups qualify for the addition of Signed-of-by in my other
changes. I also expect at least one more cleanup patch (a rename so the
recipe nomenclature matches the GCC configuration option naming, viz.
s/fpu/float/ when determining --with-float which is different from
--with-fpu).
If my series stays live I'd be happy to add the gcc 4.9.x patch that got
Torvalds' knickers in a twist to the set.
Peter
next reply other threads:[~2014-08-14 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 8:47 Peter A. Bigot [this message]
2014-08-14 9:25 ` reconciling pending gcc recipe updates Richard Purdie
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=53EC77A2.9040809@pabigot.com \
--to=pab@pabigot.com \
--cc=openembedded-core@lists.openembedded.org \
/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