Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: please stop breaking psplash-zap!
Date: Fri, 11 Jun 2010 11:35:34 -0700	[thread overview]
Message-ID: <4C1281F6.4030505@mentor.com> (raw)
In-Reply-To: <hutusi$dno$1@dough.gmane.org>

Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> This week 2 patches have been pushed that break psplash-zap for its main
> user and creator, namely angstrom.
> 
> If you are an actual user of that recipe and you want to change it,
> please RFC it here first, I'm getting tired of doing a daily check to
> see if someone broke it without asking first *again*

http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-June/020460.html

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2010-06-11 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 18:22 please stop breaking psplash-zap! Koen Kooi
2010-06-11 18:35 ` Tom Rini [this message]
2010-06-11 19:50   ` Koen Kooi
2010-06-11 23:35     ` Andrea Adami

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=4C1281F6.4030505@mentor.com \
    --to=tom_rini@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox