Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ola x Nilsson <ola.x.nilsson@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH 2/2] externalsrc.bbclass: Avoid symlink clashes	for virtclasses
Date: Wed, 13 Sep 2017 11:26:36 +0000	[thread overview]
Message-ID: <1505301996590.67336@axis.com> (raw)
In-Reply-To: <1505299304.18640.40.camel@linuxfoundation.org>

________________________________________
> From: Richard Purdie <richard.purdie@linuxfoundation.org>
> Sent: Wednesday, September 13, 2017 12:41
>
>On Tue, 2017-09-12 at 11:23 +0000, Ola x Nilsson wrote:
>> I noticed that the preceding commit has been merged.
>>  Is there some problem with this one?
>
> Its not something I can describe easily, more a gut feeling that is
> shared by some others I've talked to.
>
> Basically externalsrc is turning into an ever more complicated pile of
> corner cases and it worries me a lot. I can't help thinking we really
> want to simplify and streamline this, not add more complexity to it.

Can't argue with that.

/Ola








      reply	other threads:[~2017-09-13 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 14:58 [PATCH 1/2] oeqa/selftest/case: Add recipeinc method Ola x Nilsson
2017-08-28 14:58 ` [PATCH 2/2] externalsrc.bbclass: Avoid symlink clashes for virtclasses Ola x Nilsson
2017-09-12 11:23   ` Ola x Nilsson
2017-09-13 10:41     ` Richard Purdie
2017-09-13 11:26       ` Ola x Nilsson [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=1505301996590.67336@axis.com \
    --to=ola.x.nilsson@axis.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=richard.purdie@linuxfoundation.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