Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] license.py: remove duplicate '&' or '|' from LICENSE
Date: Wed, 11 Jan 2012 13:56:27 +0000	[thread overview]
Message-ID: <1356479.bsRlACIzx0@helios> (raw)
In-Reply-To: <1326285902-31525-1-git-send-email-andrei@gherzan.ro>

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

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-01-11 14:04 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 [this message]
2012-01-11 14:11   ` Andrei Gherzan
2012-01-12  7:19     ` Saul Wold
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=1356479.bsRlACIzx0@helios \
    --to=paul.eggleton@linux.intel.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