From: Trevor Woerner <twoerner@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: [meta-chip][PATCH] u-boot-chip: fix md5sum
Date: Wed, 27 Apr 2016 09:23:18 -0400 [thread overview]
Message-ID: <20160427132318.GB32572@linux-yxv0> (raw)
In-Reply-To: <1460399310-15649-1-git-send-email-twoerner@gmail.com>
ping?
it's been over 2 weeks now
On Mon 2016-04-11 @ 02:28:30 PM, Trevor Woerner wrote:
> The u-boot master and chip/stable branches have diverged such that the md5sums
> of the License README files are now different. The latest master branch has
> added a "SIL OPEN FONT LICENSE (OFL-1.1)" license.
>
> diff:
> --- chip/stable-README 2016-04-10 02:05:30.783023170 -0400
> +++ upstream-README 2016-04-11 13:48:34.973027406 -0400
> @@ -67,4 +67,5 @@
> IBM PIBS (PowerPC Initialization and IBM-pibs ibm-pibs.txt
> Boot Software) license
> ISC License ISC Y isc.txt https://spdx.org/licenses/ISC
> +SIL OPEN FONT LICENSE (OFL-1.1) OFL-1.1 Y OFL.txt https://spdx.org/licenses/OFL-1.1.html
> X11 License X11 x11.txt https://spdx.org/licenses/X11.html
>
> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> ---
> recipes-bsp/u-boot/u-boot-chip_git.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/recipes-bsp/u-boot/u-boot-chip_git.bb b/recipes-bsp/u-boot/u-boot-chip_git.bb
> index 2342478..60db3e0 100644
> --- a/recipes-bsp/u-boot/u-boot-chip_git.bb
> +++ b/recipes-bsp/u-boot/u-boot-chip_git.bb
> @@ -2,6 +2,8 @@ require recipes-bsp/u-boot/u-boot.inc
>
> DESCRIPTION = "U-Boot port for C.H.I.P. boards"
>
> +LIC_FILES_CHKSUM = "file://Licenses/README;md5=0507cd7da8e7ad6d6701926ec9b84c95"
> +
> DEPENDS += "dtc-native"
> PROVIDES += "u-boot"
>
> --
> 2.7.0.rc3
>
next prev parent reply other threads:[~2016-04-27 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 18:28 [meta-chip][PATCH] u-boot-chip: fix md5sum Trevor Woerner
2016-04-22 14:26 ` Trevor Woerner
2016-04-27 13:23 ` Trevor Woerner [this message]
2016-05-06 12:35 ` Trevor Woerner
2016-05-10 14:52 ` Andrei Gherzan
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=20160427132318.GB32572@linux-yxv0 \
--to=twoerner@gmail.com \
--cc=yocto@yoctoproject.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.