Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Abbreviation of OpenEmbedded-Core
Date: Wed, 07 Dec 2011 13:30:29 -0800	[thread overview]
Message-ID: <4EDFDAF5.2080901@linux.intel.com> (raw)
In-Reply-To: <1323292609.4065.42.camel@mattotaupa>

On 07/12/11 13:16, Paul Menzel wrote:
> Dear OE folks,

OE-Core folks?

> Am Mittwoch, den 07.12.2011, 11:34 -0800 schrieb Beth Flanagan:
>> From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
>>
>> This is a quick audit of only the most obviously wrong licenses
>> found within OECore. These fixes fall into four areas:
> 
> could we agree on the spelling of the abbreviation of OpenEmbedded-Core?
> 
> In the files in the repository everything is spelled OE-Core so I guess
> that should be it. The Wiki uses OE-Core [1] and Elisabeth’s commit
> message uses OECore.

I think we do have an accord here. Consistent usage in the 'code' and
documentation emphasises that. What makes you think we don't agree?

It's probably that Elizabeth's commit message was a typo. I certainly
make enough of those.

Regards,
Joshua
-- 
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre



  reply	other threads:[~2011-12-07 21:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 19:34 [PATCH 0/8] License Consolidated Pull Beth Flanagan
2011-12-07 19:34 ` [PATCH 1/8] oe.test_types: move into an oe.tests package Beth Flanagan
2011-12-07 19:34 ` [PATCH 2/8] license: split license parsing into oe.license Beth Flanagan
2011-12-07 19:34 ` [PATCH 3/8] oe.license: add license flattening code Beth Flanagan
2011-12-07 19:34 ` [PATCH 4/8] Add copyleft compliance class Beth Flanagan
2011-12-07 21:53   ` Khem Raj
2011-12-07 22:50     ` Chris Larson
2011-12-09  2:21     ` [PATCH 4/8] Add copyleft compliance class --- MAJOR BREAKAGE!!!! Ulf Samuelsson
2011-12-09  8:24       ` Ulf Samuelsson
2011-12-09 11:45       ` Richard Purdie
2011-12-09 13:46         ` Ulf Samuelsson
2011-12-09 13:51           ` Koen Kooi
2011-12-09 20:03             ` Flanagan, Elizabeth
2011-12-09 19:53           ` Khem Raj
2011-12-07 19:34 ` [PATCH 5/8] gettext-minimal-native: Fix License Beth Flanagan
2011-12-07 19:34 ` [PATCH 6/8] [YOCTO #1776] license: manifest and license path Beth Flanagan
2011-12-09 13:30   ` Richard Purdie
2011-12-09 19:57     ` Khem Raj
2011-12-09 20:02       ` Joshua Lock
2011-12-09 21:41         ` Khem Raj
2011-12-09 23:49       ` Richard Purdie
2011-12-10  8:16       ` Koen Kooi
2011-12-10 10:29         ` Richard Purdie
2011-12-07 19:34 ` [PATCH 7/8] OECore license fixes: meta/* Beth Flanagan
2011-12-07 21:16   ` Abbreviation of OpenEmbedded-Core (was: [PATCH 7/8] OECore license fixes: meta/*) Paul Menzel
2011-12-07 21:30     ` Joshua Lock [this message]
2011-12-07 21:40       ` Abbreviation of OpenEmbedded-Core Paul Menzel
2011-12-14 16:06   ` [PATCH 7/8] OECore license fixes: meta/* Phil Blundell
2011-12-15  1:18     ` Flanagan, Elizabeth
2012-10-02 10:46   ` Phil Blundell
2012-10-02 15:16     ` Flanagan, Elizabeth
2012-10-02 16:00       ` Phil Blundell
2011-12-07 19:34 ` [PATCH 8/8] package.bbclass: Adding license collection Beth Flanagan
2011-12-08 15:25 ` [PATCH 0/8] License Consolidated Pull 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=4EDFDAF5.2080901@linux.intel.com \
    --to=josh@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