From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2 0/3] Recipe for MuPDF
Date: Wed, 23 Jun 2010 10:12:27 -0700 [thread overview]
Message-ID: <4C22407B.4060309@mentor.com> (raw)
In-Reply-To: <1277312438-326-1-git-send-email-mad_soft@inbox.ru>
Dmitry Artamonow wrote:
> As there's no more comments on original patch series[1], guess it's time
> to send v2. Do whatever you like with these patches :-)
>
> [1] http://patchwork.openembedded.org/bundle/mad_soft/mupdf-0.6-v1/
>
> Changelog v1 => v2:
>
> * removed autotools_stage_all from openjpeg and jbig2dec recipes,
> as suggested by Khem Raj
> * used upstream patch fixing endianness issues on 16-bit displays
> instead of custom hack (upstream has been very kind to fix this
> bug so quickly)
> * more verbose comment about why we need -O2
Was this answered before? Why is everything in a '-tools' package? It
looks like we have empty main packages and populated '-tools'.
--
Tom Rini
Mentor Graphics Corporation
prev parent reply other threads:[~2010-06-23 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 17:00 [PATCH v2 0/3] Recipe for MuPDF Dmitry Artamonow
2010-06-23 17:00 ` [PATCH 1/3] openjpeg-1.3: new recipe Dmitry Artamonow
2010-06-23 17:00 ` [PATCH 2/3] jbig2dec-0.11: " Dmitry Artamonow
2010-06-23 17:00 ` [PATCH 3/3] mupdf-0.6: " Dmitry Artamonow
2010-06-23 17:12 ` Tom Rini [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=4C22407B.4060309@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 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.