All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH] license.py: remove duplicate '&' or '|' from LICENSE
Date: Wed, 11 Jan 2012 23:19:11 -0800	[thread overview]
Message-ID: <4F0E896F.8020107@linux.intel.com> (raw)
In-Reply-To: <4F0D989D.4080907@gherzan.ro>

On 01/11/2012 06:11 AM, Andrei Gherzan wrote:
> On 01/11/2012 03:56 PM, Paul Eggleton wrote:
>> On Wednesday 11 January 2012 14:45:02 Andrei Gherzan wrote:
>>> Some upstream layers (ex: meta-oe) use '&&' or '||' syntax in LICENSE
>>> variable. Because of my last commit, these bbfiles are failing as
>>> LICENSE
>>> is tested with oe.license where '&&' and '||' are the bug source.
>>> The fix is to replace multiple characters of '&' or '|' with a single
>>> one.
>> Sorry to be a pain but could we not just fix those layers to use the
>> accepted
>> syntax? Doing so should be just a one-line find/sed command.
>>
>> Cheers,
>> Paul
>>
> That'd be a solution as well but because those files were accepted this
> way until now i thought that this is an accepted syntax. More, this
> would scale and give a little freedom to the developers especially for
> those that are coming from "C" part or the world. (smile)
>
I think I agree with Paul here, Beth has sent out a proposal for that 
and by making a change here may allow the bad behavior to continue.

Sau!

> ag
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



  reply	other threads:[~2012-01-12 23:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 12:45 [PATCH] license.py: remove duplicate '&' or '|' from LICENSE Andrei Gherzan
2012-01-11 13:56 ` Paul Eggleton
2012-01-11 14:11   ` Andrei Gherzan
2012-01-12  7:19     ` Saul Wold [this message]
2012-01-12 11:55       ` Andrei Gherzan

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=4F0E896F.8020107@linux.intel.com \
    --to=sgw@linux.intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.