From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Francois Perrad <fperrad@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/freetype: bump to version 2.12.0
Date: Tue, 12 Apr 2022 21:53:54 +0200 [thread overview]
Message-ID: <20220412195354.GD4029883@scaer> (raw)
In-Reply-To: <20220412180057.2709514-1-francois.perrad@gadz.org>
François, All,
On 2022-04-12 20:00 +0200, Francois Perrad spake thusly:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
I just noticed that your From (git commit author) does not match your
SoB. Can you please check that they match for future contributions,
please?
Anyway; applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/freetype/freetype.hash | 6 +++---
> package/freetype/freetype.mk | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/package/freetype/freetype.hash b/package/freetype/freetype.hash
> index 7abc3d96d..78d0ba20d 100644
> --- a/package/freetype/freetype.hash
> +++ b/package/freetype/freetype.hash
> @@ -1,8 +1,8 @@
> -# From https://sourceforge.net/projects/freetype/files/freetype2/2.11.1/
> -sha1 86bdc98b37efe447cf53420bf2c18402ff905112 freetype-2.11.1.tar.xz
> +# From https://sourceforge.net/projects/freetype/files/freetype2/2.12.0/
> +sha1 fd1eb1a27f178808e1d8ccd82c71abfa5d0ebe13 freetype-2.12.0.tar.xz
> +sha256 ef5c336aacc1a079ff9262d6308d6c2a066dd4d2a905301c4adda9b354399033 freetype-2.12.0.tar.xz
>
> # Locally calculated
> -sha256 3333ae7cfda88429c97a7ae63b7d01ab398076c3b67182e960e5684050f2c5c8 freetype-2.11.1.tar.xz
> sha256 c85e842b7ff04d95dab7d68e812773de0f8b67940e5449d35b42c66eb0f619fe LICENSE.TXT
> sha256 08c135755dd589039470f1fdbb400daaabaaa50d0b366d19cebff4d22986baa1 docs/FTL.TXT
> sha256 c4120c6752c910c299e3bd9cb3a46ff262c268303ca2069b61f92f10a5656c18 docs/GPLv2.TXT
> diff --git a/package/freetype/freetype.mk b/package/freetype/freetype.mk
> index 912e6c4da..5c6b8c73b 100644
> --- a/package/freetype/freetype.mk
> +++ b/package/freetype/freetype.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -FREETYPE_VERSION = 2.11.1
> +FREETYPE_VERSION = 2.12.0
> FREETYPE_SOURCE = freetype-$(FREETYPE_VERSION).tar.xz
> FREETYPE_SITE = http://download.savannah.gnu.org/releases/freetype
> FREETYPE_INSTALL_STAGING = YES
> --
> 2.32.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-04-12 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 18:00 [Buildroot] [PATCH] package/freetype: bump to version 2.12.0 Francois Perrad
2022-04-12 19:53 ` Yann E. MORIN [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=20220412195354.GD4029883@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
--cc=fperrad@gmail.com \
/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