Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Florian Boor <florian.boor@kernelconcepts.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] rm_work
Date: Tue, 10 Apr 2007 12:18:04 +0200	[thread overview]
Message-ID: <461B645C.5040307@kernelconcepts.de> (raw)
In-Reply-To: <CD2A5546-06FC-414A-9C74-FB640EBFC4A5@selfish.org>

Hi,

Holger Freyther schrieb:
> how many recipes still break with rm_work, is there a documentation  
> which tasks to add and link to unbreak rm_work (if it breaks). I'm  
> still uncertain if the cleaning should be done by bitbake itself.

I'm using it for some time now - the only trouble I ran into were some breaking
kernel packages. But if there are still some broken remaining these would be
easy to fix.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor@kernelconcepts.de

1D78 2D4D 6C53 1CA4 5588  D07B A8E7 940C 25B7 9A76



  parent reply	other threads:[~2007-04-10 10:18 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
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 [this message]
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=461B645C.5040307@kernelconcepts.de \
    --to=florian.boor@kernelconcepts.de \
    --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