Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] Enable bmp and JPEG files for fbv
Date: Thu, 21 Jan 2010 13:12:44 +0000	[thread overview]
Message-ID: <1264079564.9743.184.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <4B564B3D.7020108@atmel.com>

On Wed, 2010-01-20 at 01:15 +0100, Ulf Samuelsson wrote:
> Enable bmp and JPEG files for fbv
> 
> Previously only supported PNG.
> Ungif still not supported
> Remove unneccesary whitespace
> Do not install manuals to target
> 
> Signed-off-by: Ulf Samuelsson <ulf.samuelsson@atmel.com>

What's the reason for not installing the manuals?  That seems like a
retrograde step.

p.





  parent reply	other threads:[~2010-01-21 13:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20  0:15 [PATCH v2] Enable bmp and JPEG files for fbv Ulf Samuelsson
2010-01-20  6:43 ` Marcin Juszkiewicz
2010-01-20  9:37 ` Paul Menzel
2010-01-26 21:04   ` Tom Rini
2010-01-21 12:43 ` Philip Balister
2010-01-21 13:12 ` Phil Blundell [this message]
2010-01-22  9:05 ` Graeme Gregory
2010-01-22 13:08   ` Paul Menzel
2010-01-23  9:08 ` 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=1264079564.9743.184.camel@mill.internal.reciva.com \
    --to=philb@gnu.org \
    --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