From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: current state of OE dev branch?
Date: Thu, 14 Jan 2010 09:45:36 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001140943220.2609@localhost> (raw)
later today, i'll take another shot at building the BB-demo-image.
based on whatever gets "git pull"ed at the time, is there any
still-known breakage? in my case, for f12 since i know full well that
other distros sometimes have no problem.
before i try to build, i'll clean e2fsprogs, mplayer and ffmpeg,
which were the packages causing so much grief lately. thanks.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next reply other threads:[~2010-01-14 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 14:45 Robert P. J. Day [this message]
2010-01-14 18:27 ` current state of OE dev branch? Koen Kooi
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=alpine.LFD.2.00.1001140943220.2609@localhost \
--to=rpjday@crashcourse.ca \
--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