Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-core@lists.openembedded.org
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: OE Github repositories
Date: Mon, 28 Apr 2014 14:45:26 +0200	[thread overview]
Message-ID: <ljlih4$rvg$1@ger.gmane.org> (raw)
In-Reply-To: <3327056.Df3VZKvVg7@peggleto-mobl5.ger.corp.intel.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Eggleton schreef op 28-04-14 13:08:
> On Monday 28 April 2014 12:43:58 Koen Kooi wrote:
>> Op 28 apr. 2014, om 12:10 heeft Paul Eggleton
> <paul.eggleton@linux.intel.com> het volgende
> geschreven:
>>> Hi folks,
>>> 
>>> Could whoever has admin access for the OpenEmbedded repositories on
>>> github please do two things:
>>> 
>>> 1) Stop having both "oe-core" and "openembedded-core" repositories -
>>> the latter is four months out-of-date. I'd suggest if we want to be
>>> consistent with our openembedded.org repos we should keep the
>>> "openembedded-core" repository and make it so it is kept up-to-date.
>>> 
>>> 2) Rename the "meta-oe" repository to "meta-openembedded", since
>>> meta-oe the layer is distinct from meta-openembedded the repository,
>>> and again this would be consistent with the primary repository
>>> naming.
>> 
>> Keep in mind that renaming/removing 'oe-core' and 'meta-oe' will
>> breaks things which use those repos to pull from by default. Which the
>> oe.org git server has improved a lot, it still can't beat githubs CDN.
> 
> OK then, how about this instead:
> 
> 1) Ensure the "openembedded-core" repository is kept up-to-date
> 
> 2) Add a "meta-openembedded" repository and ensure it is kept up-to-date
> 
> 3) Add a warning to the description for the contracted name repositories
> that the fully-named repositories should be used instead, so we can
> eventually drop them
> 
> 4) Change documentation / scripts to match #3

Sounds like a good plan to me!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFTXk1mMkyGM64RGpERAn8NAJ49r8TimCZIouIBM45jseXqA3xUCACdGPsh
jb5olKQRlsskP9x4vlmEIms=
=FqlW
-----END PGP SIGNATURE-----



  reply	other threads:[~2014-04-28 12:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 10:10 OE Github repositories Paul Eggleton
2014-04-28 10:43 ` Koen Kooi
2014-04-28 11:08   ` Paul Eggleton
2014-04-28 12:45     ` Koen Kooi [this message]
2014-05-16 10:51       ` Paul Eggleton
2014-05-16 10:52         ` [oe] " Phil Blundell
2014-05-16 12:48           ` Philip Balister
2014-05-18 19:01         ` Phil Blundell
2014-05-19  9:09           ` Paul Eggleton

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='ljlih4$rvg$1@ger.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@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