From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] New stable branch (and maybe a new process?)
Date: Tue, 20 Jul 2010 23:09:59 +0100 [thread overview]
Message-ID: <1279663799.22581.1586.camel@rex> (raw)
In-Reply-To: <20100720190410.GM1512@excalibur.local>
On Tue, 2010-07-20 at 21:04 +0200, Stefan Schmidt wrote:
> Hello.
>
> On Tue, 2010-07-20 at 20:42, Koen Kooi wrote:
> >
> > On 20-07-10 19:34, Stefan Schmidt wrote:
> > >
> > > 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
>
> Ha, there it was. :)
>
> > It includes beasts like perl and python.
>
> Hmm, that would be tricky. But there are some more easier ones that could get
> nucked before.
Poky has removed legacy staging for perl and python so it is possible
and there is an example out there...
Cheers,
Richard
next prev parent reply other threads:[~2010-07-20 22:10 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 [this message]
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
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=1279663799.22581.1586.camel@rex \
--to=rpurdie@rpsys.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox