From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe 0/3] replace meta-oe's update-fonts.bbclass by oe-core's fontcache.bbclass
Date: Sat, 16 Feb 2013 19:33:22 +0100 [thread overview]
Message-ID: <20130216183322.GY3300@jama> (raw)
In-Reply-To: <1360622110-15419-1-git-send-email-schnitzeltony@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 2353 bytes --]
On Mon, Feb 11, 2013 at 11:35:07PM +0100, Andreas Müller wrote:
> The following changes since commit 61911b23099c2658186179504ded318c987b5276:
>
> ttf: introduce update-fonts bbclass and change all ttf recipes to use it (2013-02-06 15:16:01 +0100)
>
> are available in the git repository at:
> git://gitorious.org/schnitzeltony-oe-meta/meta-openembedded.git font-cache
>
> Andreas Müller (3):
> ttf-fonts: inherit oe-core's fontcache.bbclass instead of update-fonts
> update-fonts.bbclass: remove - we now use oe-core's fontcache.bbclass Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
> font-update-common: remove
darn, I should have noticed that fontcache has the same functionality
before introducing update-fonts. Thanks for cleanup, applied.
>
> meta-oe/classes/update-fonts.bbclass | 40 --------------------
> .../font-update-common/update-fonts | 4 --
> .../font-update-common/font-update-common_0.1.bb | 18 ---------
> .../ttf-fonts/ttf-arphic-uming_20080216.bb | 4 +-
> .../recipes-graphics/ttf-fonts/ttf-dejavu_2.23.bb | 4 +-
> .../recipes-graphics/ttf-fonts/ttf-droid_git.bb | 4 +-
> .../recipes-graphics/ttf-fonts/ttf-gentium_1.02.bb | 4 +-
> .../ttf-fonts/ttf-hunkyfonts_0.3.0.bb | 4 +-
> .../ttf-fonts/ttf-liberation_0.2.bb | 4 +-
> .../recipes-graphics/ttf-fonts/ttf-mplus_027.bb | 7 +--
> .../ttf-fonts/ttf-sazanami_20040629.bb | 4 +-
> .../ttf-fonts/ttf-ubuntu-font-family_0.80.bb | 4 +-
> .../ttf-fonts/ttf-wqy-zenhei_0.6.26.bb | 4 +-
> meta-oe/recipes-graphics/ttf-fonts/ttf.inc | 2 +-
> 14 files changed, 21 insertions(+), 86 deletions(-)
> delete mode 100644 meta-oe/classes/update-fonts.bbclass
> delete mode 100644 meta-oe/recipes-graphics/font-update-common/font-update-common/update-fonts
> delete mode 100644 meta-oe/recipes-graphics/font-update-common/font-update-common_0.1.bb
>
> --
> 1.7.4.4
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-02-16 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 22:35 [meta-oe 0/3] replace meta-oe's update-fonts.bbclass by oe-core's fontcache.bbclass Andreas Müller
2013-02-11 22:35 ` [meta-oe 1/3] ttf-fonts: inherit oe-core's fontcache.bbclass instead of update-fonts Andreas Müller
2013-02-11 22:35 ` [meta-oe 2/3] update-fonts.bbclass: remove - we now use oe-core's fontcache.bbclass Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> Andreas Müller
2013-02-11 22:39 ` Martin Jansa
2013-02-11 22:35 ` [meta-oe 3/3] font-update-common: remove Andreas Müller
2013-02-16 18:33 ` Martin Jansa [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=20130216183322.GY3300@jama \
--to=martin.jansa@gmail.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