From: Rod Whitby <rod@whitby.id.au>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] rm_work
Date: Sat, 07 Apr 2007 21:55:45 +0930 [thread overview]
Message-ID: <46178DC9.1000207@whitby.id.au> (raw)
In-Reply-To: <4617753E.409@dominion.kabel.utwente.nl>
Koen Kooi wrote:
> Holger Freyther schreef:
>>> how many recipes still break with rm_work
>
> angstrom-x11-image, angstrom-console-image and openmoko-devel-image work for various machines.
All recipes used by nslu2-linux are compatible with rm_work - we use it
on our autobuilders.
-- Rod
next prev parent reply other threads:[~2007-04-07 12:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-07 10:11 [RFC] rm_work Koen Kooi
2007-04-07 10:34 ` Holger Freyther
2007-04-07 10:41 ` Koen Kooi
2007-04-07 12:25 ` Rod Whitby [this message]
2007-04-07 22:03 ` Holger Freyther
2007-04-08 12:07 ` Koen Kooi
2007-04-08 12:21 ` Koen Kooi
2007-04-10 11:31 ` Michael 'Mickey' Lauer
2007-04-08 16:17 ` Richard Purdie
2007-04-11 6:50 ` Marcin Juszkiewicz
2007-04-11 6:55 ` Marcin Juszkiewicz
2007-04-11 8:41 ` Richard Purdie
2007-04-13 19:27 ` Koen Kooi
2007-04-13 22:08 ` Richard Purdie
2007-04-10 10:18 ` Florian Boor
2007-04-08 16:13 ` Richard Purdie
2007-04-08 17:01 ` Koen Kooi
2007-04-08 21:58 ` Richard Purdie
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=46178DC9.1000207@whitby.id.au \
--to=rod@whitby.id.au \
--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