All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Cc: Leon Woestenberg <leonw@mailcan.com>
Subject: Re: How should OE be used?
Date: Mon, 24 Sep 2007 12:35:26 -0400	[thread overview]
Message-ID: <46F7E74E.7020402@balister.org> (raw)
In-Reply-To: <46F7DDF7.8060804@am.sony.com>

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

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 :)

Philip

Tim Bird wrote:
> Leon Woestenberg wrote:
>> I became an OE user when I found that OE automated a lot more than
>> buildroot when I started adding packages. After that experience I
>> decided to use OE at work.
> ...
> 
> Leon,
> 
> I found the description of your experiences with OpenEmbedded
> and your list of issues to be very valuable.
> 
> I have added your message text to the elinux wiki at:
> http://elinux.org/Open_Embedded
> 
> I hope this is OK with you. Please let me know if there is any
> problem with this.
> 
>  -- Tim
> 
> =============================
> Tim Bird
> Architecture Group Chair, CE Linux Forum
> Senior Staff Engineer, Sony Corporation of America
> =============================
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2007-09-24 16:39 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 [this message]
2007-09-24 17:14       ` Tim Bird
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=46F7E74E.7020402@balister.org \
    --to=philip@balister.org \
    --cc=leonw@mailcan.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.