All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Phil Blundell <pb@pbcl.net>,  openembedded-core@lists.openembedded.org
Subject: Re: [oe] OE Github repositories
Date: Fri, 16 May 2014 08:48:03 -0400	[thread overview]
Message-ID: <53760903.5000907@balister.org> (raw)
In-Reply-To: <1400237551.5524.18.camel@phil-desktop.brightsign>

On 05/16/2014 06:52 AM, Phil Blundell wrote:
> On Fri, 2014-05-16 at 11:51 +0100, Paul Eggleton wrote:
>> On Monday 28 April 2014 14:45:26 Koen Kooi wrote:
>>> Paul Eggleton schreef op 28-04-14 13:08:
>>>> 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!
>>
>> OK, so who will do this then (whoever has access)?
> 
> I can do it if you like.

Thanks for taking care of this.

Philip

> 
> p.
> 
> 


  reply	other threads:[~2014-05-16 12:48 UTC|newest]

Thread overview: 12+ 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 10:43   ` [OE-core] " Koen Kooi
2014-04-28 11:08   ` Paul Eggleton
2014-04-28 11:08     ` [OE-core] " Paul Eggleton
2014-04-28 12:45     ` Koen Kooi
2014-05-16 10:51       ` Paul Eggleton
2014-05-16 10:51         ` [OE-core] " Paul Eggleton
2014-05-16 10:52         ` [oe] " Phil Blundell
2014-05-16 12:48           ` Philip Balister [this message]
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=53760903.5000907@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pb@pbcl.net \
    /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.