All of lore.kernel.org
 help / color / mirror / Atom feed
* meta-oe branch for edison?
@ 2011-12-08 20:01 McClintock Matthew-B29882
  2011-12-09 11:51 ` Richard Purdie
  0 siblings, 1 reply; 8+ messages in thread
From: McClintock Matthew-B29882 @ 2011-12-08 20:01 UTC (permalink / raw)
  To: yocto@yoctoproject.org

Hi all,

Can we create a meta-oe repo in git.yoctoproject.org? 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)

-M


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: meta-oe branch for edison?
  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
  0 siblings, 1 reply; 8+ messages in thread
From: Richard Purdie @ 2011-12-09 11:51 UTC (permalink / raw)
  To: McClintock Matthew-B29882; +Cc: yocto@yoctoproject.org

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.

Cheers,

Richard



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: meta-oe branch for edison?
  2011-12-09 11:51 ` Richard Purdie
@ 2011-12-09 15:46   ` McClintock Matthew-B29882
  2011-12-09 16:20     ` Richard Purdie
  2011-12-09 19:55     ` Khem Raj
  0 siblings, 2 replies; 8+ messages in thread
From: McClintock Matthew-B29882 @ 2011-12-09 15:46 UTC (permalink / raw)
  To: Richard Purdie; +Cc: McClintock Matthew-B29882, yocto@yoctoproject.org

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.

-M


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: meta-oe branch for edison?
  2011-12-09 15:46   ` McClintock Matthew-B29882
@ 2011-12-09 16:20     ` Richard Purdie
  2011-12-09 16:36       ` Philip Balister
  2011-12-09 19:55     ` Khem Raj
  1 sibling, 1 reply; 8+ messages in thread
From: Richard Purdie @ 2011-12-09 16:20 UTC (permalink / raw)
  To: McClintock Matthew-B29882; +Cc: yocto@yoctoproject.org

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



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: meta-oe branch for edison?
  2011-12-09 16:20     ` Richard Purdie
@ 2011-12-09 16:36       ` Philip Balister
  2011-12-10  0:10         ` Richard Purdie
  0 siblings, 1 reply; 8+ messages in thread
From: Philip Balister @ 2011-12-09 16:36 UTC (permalink / raw)
  To: Richard Purdie; +Cc: McClintock Matthew-B29882, yocto@yoctoproject.org

On 12/09/2011 11:20 AM, Richard Purdie wrote:
> 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.

We should probably have this discussion on the oe list.

Basically, we should have a way to create a "stable" branch for oe-core
and meta-oe. There also needs to be some "policy" in place for commits.
The primary concern is making sure the development branches get all
needed fixes that go into the branches.

Philip


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: meta-oe branch for edison?
  2011-12-09 15:46   ` McClintock Matthew-B29882
  2011-12-09 16:20     ` Richard Purdie
@ 2011-12-09 19:55     ` Khem Raj
  2011-12-10  5:44       ` McClintock Matthew-B29882
  1 sibling, 1 reply; 8+ messages in thread
From: Khem Raj @ 2011-12-09 19:55 UTC (permalink / raw)
  To: McClintock Matthew-B29882; +Cc: yocto@yoctoproject.org

On Fri, Dec 9, 2011 at 7:46 AM, McClintock Matthew-B29882
<B29882@freescale.com> wrote:
>> 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.

essentially you are asking for meta-oe release. I think layers dont
release in conjunction with oe-core but it would be beneficial if they
had similar time frames.


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: meta-oe branch for edison?
  2011-12-09 16:36       ` Philip Balister
@ 2011-12-10  0:10         ` Richard Purdie
  0 siblings, 0 replies; 8+ messages in thread
From: Richard Purdie @ 2011-12-10  0:10 UTC (permalink / raw)
  To: Philip Balister; +Cc: McClintock Matthew-B29882, yocto@yoctoproject.org

On Fri, 2011-12-09 at 11:36 -0500, Philip Balister wrote:
> On 12/09/2011 11:20 AM, Richard Purdie wrote:
> > 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.
> 
> We should probably have this discussion on the oe list.
> 
> Basically, we should have a way to create a "stable" branch for oe-core
> and meta-oe. There also needs to be some "policy" in place for commits.
> The primary concern is making sure the development branches get all
> needed fixes that go into the branches.

There is a 2011-1 branch in oe-core and there is going to be an update
policy of bugfixes but not upgrades or new features for that.

Cheers,

Richard



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: meta-oe branch for edison?
  2011-12-09 19:55     ` Khem Raj
@ 2011-12-10  5:44       ` McClintock Matthew-B29882
  0 siblings, 0 replies; 8+ messages in thread
From: McClintock Matthew-B29882 @ 2011-12-10  5:44 UTC (permalink / raw)
  To: Khem Raj; +Cc: McClintock Matthew-B29882, yocto@yoctoproject.org

On Fri, Dec 9, 2011 at 1:55 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Fri, Dec 9, 2011 at 7:46 AM, McClintock Matthew-B29882
> <B29882@freescale.com> wrote:
>>> 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.
>
> essentially you are asking for meta-oe release. I think layers dont
> release in conjunction with oe-core but it would be beneficial if they
> had similar time frames.

A release is one thing, just a simple tag or branch so people know
where to go to get started with specific releases.

-M


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2011-12-10  5:45 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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

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.