From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] beagleboard-olddemo-image: saved off beagleboard-demo-image
Date: Tue, 17 Aug 2010 13:41:09 -0700 [thread overview]
Message-ID: <4C6AF3E5.90502@balister.org> (raw)
In-Reply-To: <AANLkTik73cayAjmykmJvp8KqsJ_XrBfQTOkM8MJWydsP@mail.gmail.com>
On 08/17/2010 12:54 PM, Frans Meulenbroeks wrote:
> 2010/8/17 Jason Kridner<jkridner@beagleboard.org>:
>> I want to use the name beagleboard-demo-image for what actually ships
>> with the xM boards.
....
>> +inherit image
>> --
>
> What about a better name? E.g. XM-demo-iimage?
>
> And to widen the question: do we want to maintain customer/supplier
> specific images in the oe repo?
> The company I work for also has some images, but for now we opted to
> keep them in a private overlay.
In this case, beagleboard.org points people at oe dev to do builds, so
it is appropriate to have this image in dev.
I do think they should just edit the existing file, no need to save the
old one. I suspect that 90% of people using the beagle build images from
narcissus anyway.
Philip
prev parent reply other threads:[~2010-08-17 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 19:21 [PATCH] beagleboard-test-image: add g_ether kernel module Jason Kridner
2010-08-17 19:21 ` [PATCH] beagleboard-olddemo-image: saved off beagleboard-demo-image Jason Kridner
2010-08-17 19:21 ` [PATCH] beagleboard-demo-image: add packages used at ESC Jason Kridner
2010-08-17 19:54 ` [PATCH] beagleboard-olddemo-image: saved off beagleboard-demo-image Frans Meulenbroeks
2010-08-17 20:31 ` Jason Kridner
2010-08-17 21:01 ` Frans Meulenbroeks
2010-08-17 21:13 ` Jason Kridner
2010-08-17 21:13 ` Paul Menzel
2010-08-17 20:41 ` Philip Balister [this message]
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=4C6AF3E5.90502@balister.org \
--to=philip@balister.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