From: butters <butters@station51.net>
To: openembedded-devel@lists.openembedded.org
Subject: Broken recipes
Date: Sun, 30 May 2010 14:51:24 +0200 [thread overview]
Message-ID: <4C025F4C.7010305@station51.net> (raw)
In-Reply-To: <4C01BFA7.5040800@freyther.de>
Hi there,
Can someone tell me the reason for keeping broken recipes in the tree?
Examples are the maemo task and image, the openmoko task doesn't compile
because its missing stuff. Are these things going to eventually be
fixed, or are they there for some other reason that I'm not
understanding? I'm not trying to be insulting to anyone, but I think
having broken things that don't even make it to the compile stage in the
tree will confuse a lot of people.
Thanks,
Bill
next prev parent reply other threads:[~2010-05-30 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 9:37 Faking sign offs is bad Koen Kooi
2010-05-29 10:58 ` Frans Meulenbroeks
2010-05-29 11:14 ` Andrea Adami
2010-05-30 1:30 ` Holger Freyther
2010-05-30 12:51 ` butters [this message]
2010-05-30 13:14 ` Broken recipes Dr. Michael Lauer
2010-05-30 13:23 ` butters
2010-05-29 11:15 ` Faking sign offs is bad Andrea Adami
2010-05-29 17:09 ` Andrea Adami
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=4C025F4C.7010305@station51.net \
--to=butters@station51.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