All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org,
	Leon Woestenberg <leonw@mailcan.com>,
	Matthew Locke <matt@nomadgs.com>
Subject: Re: How should OE be used?
Date: Mon, 24 Sep 2007 10:14:40 -0700	[thread overview]
Message-ID: <46F7F080.90102@am.sony.com> (raw)
In-Reply-To: <46F7E74E.7020402@balister.org>

Philip Balister wrote:
> Tim,
> 
> Hopefully, we can address some of Leon's and other's issues during OEDEM
> in two weeks. So be prepared to update the elinux.org web page :)

I'll be glad to. :-)

BTW - I still have some unspent money from CELF budgeted for OE
improvements (not a lot, but some).  Also, I have a machine dedicated
in the CELF test lab for OE work.  Last year, Marcin did some contract
work for us.  I don't think we're leveraging what he did very well.
In terms of what CELF is interested in going forward: we would very
much like to see well-maintained minimal distribution that works
on several architectures.  I can use some of the above
resources for this work.

I don't want to discuss numbers on an open list, but details
are available upon request.

Can you please factor this into the OEDEM discussions?

I won't be at OEDEM, but I'll be at ELCE in Austria, November 2-3.
(see http://www.celinux.org/elc_europe07/elc_europe_index.html)
Matt Locke will be giving a talk on Open Embedded there.  I'm not
sure where the main OE developers are located in Europe, but if
it's convenient, it would be nice to meet there and discuss what
CELF can do to help out.
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================




  reply	other threads:[~2007-09-24 17:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-22 21:24 How should OE be used? Philip Balister
2007-09-23 11:19 ` Leon Woestenberg
2007-09-23 12:33   ` Koen Kooi
2007-09-24 17:20     ` Tim Bird
2007-09-24 17:43       ` Koen Kooi
2007-09-24 18:01         ` Tim Bird
2007-09-24 15:55   ` Tim Bird
2007-09-24 16:35     ` Philip Balister
2007-09-24 17:14       ` Tim Bird [this message]
2007-09-24 18:04     ` Leon Woestenberg
2007-09-24 19:23       ` Koen Kooi
2007-09-24 14:48 ` Darcy Watkins
2007-09-25 12:19   ` Stelios Koroneos
2007-09-25 15:15     ` Koen Kooi
2007-09-25 20:54     ` Darcy Watkins
2007-09-24 16:14 ` Cliff Brake
2007-09-24 18:36 ` Craig Hughes
2007-09-24 19:27   ` Philip Balister
2007-09-24 21:37   ` Richard Purdie
2007-09-24 18:48 ` Lorn Potter
2007-09-24 19:01   ` Craig Hughes
2007-09-24 19:39     ` Lorn Potter
2007-09-24 20:33       ` Craig Hughes
2007-09-24 20:52   ` Richard Purdie
2007-09-24 21:11     ` Lorn Potter
2007-09-24 22:35       ` 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=46F7F080.90102@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=leonw@mailcan.com \
    --cc=matt@nomadgs.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 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.