From: Koen Kooi <koen.kooi@linaro.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH] package.bbclass: fix strip and split logic
Date: Tue, 04 Feb 2014 12:01:18 +0100 [thread overview]
Message-ID: <52F0C87E.5040007@linaro.org> (raw)
In-Reply-To: <1521180.2sXy9KK50E@peggleto-mobl5.ger.corp.intel.com>
On 02/04/2014 11:10 AM, Paul Eggleton wrote:
> On Tuesday 04 February 2014 09:58:47 Koen Kooi wrote:
>> What's the status on this? I know a fix went into meta-intel (albeit it
>> in a legally questionable way, but that's their problem) and the other
>> affected layers have received patches for it.
>
> Legally questionable in what way? If you refer to your name being removed from
> the patch, that was rectified before the patch was merged.
Good, the last I heard was that Tom merged the patches where authorship
was removed due to "git workflow issues". I just checked meta-intel git
and it seems to be OK now.
I still don't get how someone can (accidentally or not) add
--reset-author their git patch workflow, but that's a different discussion.
--
Koen Kooi
Builds and Baselines | Release Manager
Linaro.org | Open source software for ARM SoCs
prev parent reply other threads:[~2014-02-04 11:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 9:47 [RFC][PATCH] package.bbclass: fix strip and split logic Koen Kooi
2014-01-21 13:57 ` Richard Purdie
2014-01-21 14:03 ` Koen Kooi
2014-01-21 15:04 ` Mark Hatle
2014-01-21 15:09 ` Richard Purdie
2014-01-23 9:34 ` Koen Kooi
2014-01-23 11:33 ` Otavio Salvador
2014-01-23 12:41 ` Martin Jansa
2014-02-04 8:58 ` Koen Kooi
2014-02-04 9:32 ` Richard Purdie
2014-02-04 11:20 ` Otavio Salvador
2014-02-04 11:27 ` Koen Kooi
2014-02-04 12:12 ` Otavio Salvador
2014-02-04 10:10 ` Paul Eggleton
2014-02-04 11:01 ` Koen Kooi [this message]
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=52F0C87E.5040007@linaro.org \
--to=koen.kooi@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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