From: Andy Wilcox <andy@protium.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev rootfs_ipk: as per OE, policy: remove feed management tools
Date: Thu, 01 Mar 2007 17:14:27 -0800 [thread overview]
Message-ID: <45E77A73.5020800@protium.com> (raw)
Mickey writes:
>
> Guys, please don't play games. Since it is a handy feature indeed,
> can we perhaps agree on making this a seperate bbclass to keep both of
> you satisfied?
>
Agreed. Any big behavior change like this should have much more discussion.
It might be wrong, but sometimes bugs become features. Get used to it.
Feed generation is one way I sold OE internally and one reason why
it is so terribly useful. If it has to come out for some policy, then
perhaps the
policy should be revisited.
Kind Regards,
Andy
next reply other threads:[~2007-03-02 1:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 1:14 Andy Wilcox [this message]
2007-03-02 8:22 ` [oe-commits] org.oe.dev rootfs_ipk: as per OE, policy: remove feed management tools Stelios Koroneos
2007-03-02 9:25 ` Rod Whitby
2007-03-02 10:00 ` Koen Kooi
2007-03-03 17:19 ` Matthias Hentges
2007-03-03 22:47 ` Richard Purdie
2007-03-04 0:08 ` Matthias Hentges
2007-03-04 10:42 ` Richard Purdie
2007-03-02 9:47 ` Koen Kooi
2007-03-03 19:22 ` Richard Purdie
2007-03-04 8:43 ` Koen Kooi
2007-03-04 10:59 ` Richard Purdie
2007-03-04 11:31 ` Koen Kooi
2007-03-04 14:49 ` Matthias Hentges
2007-03-04 15:01 ` Koen Kooi
2007-03-04 15:10 ` Øyvind Repvik
2007-03-09 10:54 ` [RFC] bogofeed creation Rod Whitby
2007-03-09 11:12 ` Richard Purdie
2007-03-09 13:13 ` Rod Whitby
[not found] <E1HMgkl-0004SM-Gs@linuxtogo.org>
2007-03-01 15:55 ` [oe-commits] org.oe.dev rootfs_ipk: as per OE policy: remove feed management tools Michael 'Mickey' Lauer
2007-03-01 16:23 ` Koen Kooi
2007-03-01 17:21 ` Hans Henry von Tresckow
2007-03-02 0:07 ` Hans Henry von Tresckow
2007-03-02 0:17 ` Richard Purdie
2007-03-02 0:39 ` Rod Whitby
2007-03-02 0:33 ` Matthias Hentges
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=45E77A73.5020800@protium.com \
--to=andy@protium.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.