Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: current state of OE dev branch?
Date: Thu, 14 Jan 2010 19:27:55 +0100	[thread overview]
Message-ID: <hinnna$sc1$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1001140943220.2609@localhost>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14-01-10 15:45, Robert P. J. Day wrote:
> 
>   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.

I'll push a patch for the mplayer addrinfo stuff later today.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLT2IrMkyGM64RGpERAiA6AJwK6Up4smr4U6JNg844q9lo1LEJagCfR/Nk
mFipSNvFjbcpbI4hYQnYVlE=
=J2G0
-----END PGP SIGNATURE-----




      reply	other threads:[~2010-01-14 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14 14:45 current state of OE dev branch? Robert P. J. Day
2010-01-14 18:27 ` Koen Kooi [this message]

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='hinnna$sc1$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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