From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Checkin policy??
Date: Mon, 26 Jul 2010 21:30:05 -0600 [thread overview]
Message-ID: <4C4E52BD.1080108@mlbassoc.com> (raw)
In-Reply-To: <AANLkTikRqVrJ6uS9njZm9CWW8FkVJZyZ6MbbOQ=BQuCQ@mail.gmail.com>
On 07/26/2010 09:17 PM, Chris Larson wrote:
> On Mon, Jul 26, 2010 at 8:08 PM, Gary Thomas<gary@mlbassoc.com> wrote:
>
>> Surely, there must not be any or else simple compile errors wouldn't get
>> through :-(
>>
>
> It's a trunk/master branch, shit happens, and it's not reasonable to test
> every recipe for every target for each commit. In addition, in this
> particular case, it's highly unlikely a review would have caught this error
> anyway. Fix incoming.
Fair enough, but it shows the need for something in between the
"stable" angstrom/2009 tree which is incredibly stale and the
absolute bleeding edge which changes hourly and is often too
unstable to use.
Thanks for the quick fix (testing now)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-07-27 3:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 3:08 Checkin policy?? Gary Thomas
2010-07-27 3:17 ` Chris Larson
2010-07-27 3:30 ` Gary Thomas [this message]
2010-07-27 7:16 ` Frans Meulenbroeks
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=4C4E52BD.1080108@mlbassoc.com \
--to=gary@mlbassoc.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.