From: Russell Morris <openembedded@rkmorris.us>
To: openembedded-devel@lists.openembedded.org
Cc: openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] Populating meta-oe with new patches on oe.dev
Date: Sat, 16 Jul 2011 08:25:38 -0500 [thread overview]
Message-ID: <1310822738895594500@rkmorris.us> (raw)
In-Reply-To: <CAMKF1spOJJP=qdDbYpcnArUR1rjvJznXXiB7KAqQNT5R7J8N_Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]
Hi,
My apologies for the dumb question, but I admit that I don't know the answer, so ...
Can someone explain the differences between oe-core and OpenEmbedded, and in particular the various git repositories? I ask because I'm struggling to get OE running on my h1940 (using openembedded), but I have a feeling that this may be the wrong repository to use ... but I just don't know ... :-(. I'm also not sure which ones are being worked on going forward (as I would like to submit changes once I get things working, but again don't know which repository is the right one).
Thanks in advance for your help!
... Russell
On Fri, 07/15/2011 04:42 PM, Khem Raj <raj.khem@gmail.com> wrote:
>
Hello
>
> As we all know that next release of OpenEmbedded is slated based on
> oe-core, I would like to request submitters and committers of
> the patches for oe.dev to port the patches to meta-oe or any other
> layer that is suitable for a given patch. Any new recipes
> being added to oe.dev should definitely go into the new layered structure
>
> Please follow the commit guidelines for meta-oe/oe-core and submit the
> appropriate pull requests so that when we cut out the next release we
> don't miss any of those patches.
>
> Thanks for your cooperation and help
>
> -Khem
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
[-- Attachment #2: Type: text/html, Size: 2403 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Russell Morris <openembedded@rkmorris.us>
To: openembedded-devel@lists.openembedded.org
Cc: openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Populating meta-oe with new patches on oe.dev
Date: Sat, 16 Jul 2011 08:25:38 -0500 [thread overview]
Message-ID: <1310822738895594500@rkmorris.us> (raw)
In-Reply-To: <CAMKF1spOJJP=qdDbYpcnArUR1rjvJznXXiB7KAqQNT5R7J8N_Q@mail.gmail.com>
Hi,
My apologies for the dumb question, but I admit that I don't know the answer, so ...
Can someone explain the differences between oe-core and OpenEmbedded, and in particular the various git repositories? I ask because I'm struggling to get OE running on my h1940 (using openembedded), but I have a feeling that this may be the wrong repository to use ... but I just don't know ... :-(. I'm also not sure which ones are being worked on going forward (as I would like to submit changes once I get things working, but again don't know which repository is the right one).
Thanks in advance for your help!
... Russell
On Fri, 07/15/2011 04:42 PM, Khem Raj <raj.khem@gmail.com> wrote:
>
Hello
>
> As we all know that next release of OpenEmbedded is slated based on
> oe-core, I would like to request submitters and committers of
> the patches for oe.dev to port the patches to meta-oe or any other
> layer that is suitable for a given patch. Any new recipes
> being added to oe.dev should definitely go into the new layered structure
>
> Please follow the commit guidelines for meta-oe/oe-core and submit the
> appropriate pull requests so that when we cut out the next release we
> don't miss any of those patches.
>
> Thanks for your cooperation and help
>
> -Khem
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
From openembedded@rkmorris.us Sat Jul 16 16:30:15 2011
Received: from vms173005pub.verizon.net ([206.46.173.5])
by linuxtogo.org with esmtp (Exim 4.72)
(envelope-from <openembedded@rkmorris.us>)
id 1Qi5sl-0004mB-6b; Sat, 16 Jul 2011 16:30:15 +0200
Received: from server ([unknown] [173.74.34.213]) by vms173005.mailsrvcs.net
(Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16
2009))
with ESMTPA id <0LOF0050PHAVWSA0@vms173005.mailsrvcs.net>; Sat,
16 Jul 2011 08:25:45 -0500 (CDT)
Received: from server (127.0.0.1) by server (Axigen)
with ESMTPSA id 16FE58; Sat, 16 Jul 2011 08:25:40 -0500
Received: from [192.168.1.13] by rkmorris.us with HTTP; Sat,
16 Jul 2011 08:25:38 -0500
From: Russell Morris <openembedded@rkmorris.us>
Date: Sat, 16 Jul 2011 08:25:38 -0500
X-Mailer: Axigen WebMail
To: openembedded-devel@lists.openembedded.org
Message-id: <1310822738895594500@rkmorris.us>
In-reply-to: <CAMKF1spOJJP
next prev parent reply other threads:[~2011-07-16 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 21:42 Populating meta-oe with new patches on oe.dev Khem Raj
2011-07-16 13:25 ` Russell Morris [this message]
2011-07-16 13:25 ` Russell Morris
2011-07-26 17:20 ` [oe] " Paul Eggleton
2011-07-26 17:20 ` Paul Eggleton
2011-07-17 16:12 ` Paul Menzel
2011-07-26 17:11 ` Paul Eggleton
2011-07-28 9:37 ` Phil Blundell
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=1310822738895594500@rkmorris.us \
--to=openembedded@rkmorris.us \
--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 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.