From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Insop Song <insop.song@gmail.com>
Cc: yocto@yoctoproject.org, Darren Hart <dvhart@linux.intel.com>,
Development list for the linux-yocto repositories
<linux-yocto@yoctoproject.org>
Subject: Re: A question on adding a new program to a new meta layer
Date: Mon, 11 Mar 2013 10:34:20 -0400 [thread overview]
Message-ID: <513DEB6C.7050903@windriver.com> (raw)
In-Reply-To: <CACzyEJ-YObwTGoOcLGXGiXeoLia+RdtcLmSt9gDLXJG5hBHeoA@mail.gmail.com>
On 13-03-10 11:32 PM, Insop Song wrote:
> On Sun, Mar 10, 2013 at 8:28 PM, Bruce Ashfield
>>
>> Expect that the yocto project hosted meta-realtime will appear in a
>> week or so. I'm doing the legwork at the moment, but with some travel
>> in the upcoming week, the initial push will be delayed by a few days.
>>
>> Cheers,
>>
>> Bruce
>>
>>
>
> That's great!
> I saw the place holder on the git.yoctoproject this morning.
> Please let me know if you need anything for me to do or test.
>
I've pushed a bit more of the initial layer structure to the repository.
I'm not rationalizing a few items from your existing layers, and similar
repositories into the single meta-realtime.
As an example, I have a schedtool recipe that uses the
git://gitorious.org/sched_deadline/schedtool-dl.git
repository with a 4 patch series to enable full sched_deadline/EDF
support versus the custom repository that you created on github.
We'll work to unify the edf and other -rt support in the upstream
projects, so we want to reference those trees whenever possible (unless
we get so much development, that a tracking tree makes sense).
Also, don't be concerned that I show up as the only maintainer in the
meta-realtime layer, as I merge parts from your existing layer, credit
will be given and if it is ok with you, I'll have you down as a maintainer
or co-maintainer where it makes sense.
Since I'm going to be out of the office for the next few days, I may
push out my initial merges without much testing, so if you have a
chance to test, and send patches .. that would be a great help.
Cheers,
Bruce
> Regards,
>
> Insop
>
next prev parent reply other threads:[~2013-03-11 14:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACzyEJ_3BRjn4s7ADey9uuQpGhgWKeuuyxGVL09HuLAzJ3LqTQ@mail.gmail.com>
2013-03-05 6:54 ` A question on adding a new program to a new meta layer Insop Song
2013-03-07 4:00 ` Bruce Ashfield
2013-03-07 4:24 ` Juri Lelli
2013-03-07 13:53 ` Bruce Ashfield
2013-03-07 21:49 ` Insop Song
2013-03-08 1:46 ` Bruce Ashfield
2013-03-08 4:12 ` Insop Song
2013-03-07 5:05 ` Insop Song
2013-03-07 8:26 ` Insop Song
2013-03-07 14:05 ` Bruce Ashfield
2013-03-07 22:02 ` Insop Song
2013-03-08 1:47 ` Bruce Ashfield
2013-03-08 11:10 ` Insop Song
2013-03-07 14:04 ` Bruce Ashfield
2013-03-08 13:27 ` Insop Song
2013-03-08 16:32 ` Bruce Ashfield
2013-03-08 17:03 ` Darren Hart
2013-03-08 17:36 ` Bruce Ashfield
2013-03-07 14:08 ` Bruce Ashfield
2013-03-07 21:43 ` Insop Song
2013-03-08 1:45 ` Bruce Ashfield
2013-03-08 4:02 ` Juri Lelli
2013-03-05 9:19 ` Insop Song
2013-03-08 17:01 ` Darren Hart
2013-03-08 23:35 ` Bruce Ashfield
2013-03-09 10:32 ` Insop Song
2013-03-11 3:28 ` Bruce Ashfield
2013-03-11 3:32 ` Insop Song
2013-03-11 14:34 ` Bruce Ashfield [this message]
2013-03-11 16:07 ` Insop Song
2013-03-11 17:03 ` Bruce Ashfield
2013-03-11 17:20 ` Insop Song
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=513DEB6C.7050903@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=insop.song@gmail.com \
--cc=linux-yocto@yoctoproject.org \
--cc=yocto@yoctoproject.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.