All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] New stable branch (and maybe a new process?)
Date: Tue, 20 Jul 2010 16:24:37 -0700	[thread overview]
Message-ID: <4C463035.7010100@mentor.com> (raw)
In-Reply-To: <4C462C32.40202@mentor.com>

Tom Rini wrote:
> Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 20-07-10 21:16, Tom Rini wrote:
>>> Koen Kooi wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> On 20-07-10 19:34, Stefan Schmidt wrote:
>>>>> Hello.
>>>>>
>>>>> On Tue, 2010-07-20 at 18:56, Koen Kooi wrote:
>>>>>> On 20-07-10 10:40, Stefan Schmidt wrote:
>>>>>>> So your suggestion is to wait until all three are done?
>>>>>> 'Wait' is maybe the wrong word. I would try to do a call to arms 
>>>>>> to get
>>>>>> more people interested into getting this done.
>>>>> Wasn't there a list produced with all recipes that used legacy
>>>>> staging? I swear
>>>>> I have seen something like this but I can't find it in my recent 
>>>>> builds.
>>>> In your TMPDIR:
>>>>
>>>> koen@dominion:/OE/angstrom-dev$ cat legacy-staging.log | sort | uniq |
>>>> wc -l
>>>> 53
>>>>
>>>> It includes beasts like perl and python.
>>> perl yes, python no.  Overall point, yes.
>>>
>>
>> Mine lists:
>>
>> /OE/org.openembedded.dev/recipes/perl/perl_5.8.8.bb
>> /OE/org.openembedded.dev/recipes/python/python_2.6.4.bb
>>
>> And that's from a rebuild from scratch last week.
> 
> Going off list... 
> http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=a753e680011a9843e0cd0ee928fd508667445d00 
> and I just did a -c clean and rebuild.

Welp, I fail today.  Sorry all.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2010-07-20 23:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 20:40 [RFC] New stable branch (and maybe a new process?) Stefan Schmidt
2010-07-10  6:51 ` Frans Meulenbroeks
2010-07-12  6:50   ` Stefan Schmidt
2010-07-13 18:36 ` Stefan Schmidt
2010-07-20  7:01 ` Stefan Schmidt
2010-07-20  8:09   ` Koen Kooi
2010-07-20  8:40     ` Stefan Schmidt
2010-07-20 11:20       ` Detlef Vollmann
2010-07-20 13:10       ` Philip Balister
2010-07-20 13:32         ` Stefan Schmidt
2010-07-20 16:56       ` Koen Kooi
2010-07-20 17:34         ` Stefan Schmidt
2010-07-20 18:42           ` Koen Kooi
2010-07-20 19:04             ` Stefan Schmidt
2010-07-20 22:09               ` Richard Purdie
2010-07-20 19:16             ` Tom Rini
2010-07-20 20:58               ` Koen Kooi
2010-07-20 23:07                 ` Tom Rini
2010-07-20 23:24                   ` Tom Rini [this message]
2010-07-20 21:31             ` Frans Meulenbroeks
2010-07-20 19:07           ` Esben Haabendal
2010-07-20 19:22             ` Stefan Schmidt
2010-07-21  5:58               ` Esben Haabendal
2010-07-21  7:13                 ` Frans Meulenbroeks
2010-07-22 18:40                   ` Khem Raj
2010-07-20  8:43   ` Chris Simmonds
2010-07-20 10:01     ` Robert P. J. Day
2010-07-20 10:12     ` Jaap de Jong
2010-07-20 11:06       ` Christophe Aeschlimann

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=4C463035.7010100@mentor.com \
    --to=tom_rini@mentor.com \
    --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.