From: Michael 'Mickey' Lauer <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE breakages, was: Re: fakeroot fails to build
Date: Thu, 26 Feb 2009 20:37:26 +0100 [thread overview]
Message-ID: <1235677046.2621.226.camel@andromeda> (raw)
In-Reply-To: <ac9c93b10902260920s24a8c5we592cbb4d0d63221@mail.gmail.com>
Am Donnerstag, den 26.02.2009, 18:20 +0100 schrieb Frans Meulenbroeks:
> > Maybe it's time for OE to consider whether it really wants a zillion
> > commits per day or only a few tested commits per day.
I think we want both, given the right branches. Let me again propose a
structure such as org.openembedded.{stable,testing,unstable} where only
cherry-picking from the more unstable to the lesser unstable branch is
allowed.
Note that this doesn't conflict with your idea of reviews, someone/some
people still need to decide which revs are good to cherry-pick.
> BTW, I noticed that there are a lot of bugs in bugzilla about packages
> that do not build. Most of these are old. Guess the bugs are fixed but
> no-one seems to close them.
I regularly scan the bugtracker doing my share of cleaning, more people
should do that.
--
:M:
next prev parent reply other threads:[~2009-02-26 19:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 17:20 OE breakages, was: Re: fakeroot fails to build Frans Meulenbroeks
2009-02-26 19:37 ` Michael 'Mickey' Lauer [this message]
2009-02-27 16:06 ` Leon Woestenberg
2009-02-27 16:26 ` Tom Rini
2009-02-27 17:56 ` Frans Meulenbroeks
2009-02-27 19:35 ` Tom Rini
2009-02-28 10:54 ` Frans Meulenbroeks
2009-02-28 15:53 ` Tom Rini
2009-02-28 18:07 ` Frans Meulenbroeks
2009-02-28 18:29 ` Tom Rini
2009-03-01 17:09 ` Koen Kooi
2009-03-02 18:55 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2009-02-25 6:53 Mike (mwester)
2009-02-25 7:57 ` Koen Kooi
2009-02-25 8:23 ` Michael 'Mickey' Lauer
2009-02-25 15:14 ` Mike (mwester)
2009-02-25 15:43 ` OE breakages, was: " Koen Kooi
2009-02-26 13:05 ` Bernhard Guillon
2009-02-27 19:30 ` Rodrigo Vivi
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=1235677046.2621.226.camel@andromeda \
--to=mickey@vanille-media.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 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.