From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: meta-oe branch for edison?
Date: Fri, 09 Dec 2011 16:20:37 +0000 [thread overview]
Message-ID: <1323447637.5309.180.camel@ted> (raw)
In-Reply-To: <CAEsOVNexQiXQkWQH8hEBq+4JFGihda7_azWPrxeTG9J+M3wgvw@mail.gmail.com>
On Fri, 2011-12-09 at 15:46 +0000, McClintock Matthew-B29882 wrote:
> On Fri, Dec 9, 2011 at 5:51 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Thu, 2011-12-08 at 20:01 +0000, McClintock Matthew-B29882 wrote:
> >> Hi all,
> >>
> >> Can we create a meta-oe repo in git.yoctoproject.org?
> >
> > This might create a little friction with the OE community. What would be
> > the reason for the repository?
> >
> >> I'd like to also
> >> create a branh within the repo that tracks a valid version of the repo
> >> for specific Yocto releases.
> >>
> >> (I can add that in my investigation so far -
> >> f78f3f31c06c669006fcb567c8f503d4dbec68da looks like a good starting
> >> commit for edison)
> >
> > I'd certainly be happy to see such a branch. It might be more
> > appropriate to call it 2011-1 which corresponds to the OE-Core branch
> > name that is edison in the poky repo.
>
> Well I don't particularly care if we create a repo or not. I just want
> a place to go for a working meta-oe for all future releases of Yocto.
> I had to figure this out on my own, but I'm can imagine others will
> attempt similar things.
I think it should be fine to add an appropriate branch to the meta-oe
repository itself.
Cheers,
Richard
next prev parent reply other threads:[~2011-12-09 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 20:01 meta-oe branch for edison? McClintock Matthew-B29882
2011-12-09 11:51 ` Richard Purdie
2011-12-09 15:46 ` McClintock Matthew-B29882
2011-12-09 16:20 ` Richard Purdie [this message]
2011-12-09 16:36 ` Philip Balister
2011-12-10 0:10 ` Richard Purdie
2011-12-09 19:55 ` Khem Raj
2011-12-10 5:44 ` McClintock Matthew-B29882
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=1323447637.5309.180.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=B29882@freescale.com \
--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.