From: "Yu, Mingli" <mingli.yu@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH v2] mcelog: Upgrade to 159
Date: Fri, 6 Jul 2018 16:45:15 +0800 [thread overview]
Message-ID: <5B3F2C1B.1050005@windriver.com> (raw)
In-Reply-To: <20180706084113.95133-1-mingli.yu@windriver.com>
On 2018年07月06日 16:41, mingli.yu@windriver.com wrote:
> From: Mingli Yu <mingli.yu@windriver.com>
>
> Update LIC_FILES_CHKSUM as license file README.md
> updated as below:
>
> diff a.orig/README.md a/README.md
>
> < see [mcelog.org](http://www.mcelog.org).
> ---
>> see [mcelog.org](https://www.mcelog.org).
> 56a57,60
>>
>> By default mcelog reports its version as the git tag. This can be overridden
>> by setting up a .os_release file in the source directory. A build system
>> could write the OS version to this file to mark the binary.
The message as below, seems > behaves special in email.
Update LIC_FILES_CHKSUM as license file README.md
updated as below:
diff a.orig/README.md a/README.md
< see [mcelog.org](http://www.mcelog.org).
---
> see [mcelog.org](https://www.mcelog.org).
56a57,60
>
> By default mcelog reports its version as the git tag. This can be
overridden
> by setting up a .os_release file in the source directory. A build
system
> could write the OS version to this file to mark the binary.
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
Thanks,
>
> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
> ---
> .../recipes-support/mcelog/{mcelog_1.49.bb => mcelog_159.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta-oe/recipes-support/mcelog/{mcelog_1.49.bb => mcelog_159.bb} (89%)
>
> diff --git a/meta-oe/recipes-support/mcelog/mcelog_1.49.bb b/meta-oe/recipes-support/mcelog/mcelog_159.bb
> similarity index 89%
> rename from meta-oe/recipes-support/mcelog/mcelog_1.49.bb
> rename to meta-oe/recipes-support/mcelog/mcelog_159.bb
> index 84633a76c..236ad7d00 100644
> --- a/meta-oe/recipes-support/mcelog/mcelog_1.49.bb
> +++ b/meta-oe/recipes-support/mcelog/mcelog_159.bb
> @@ -9,10 +9,10 @@ SRC_URI = "git://git.kernel.org/pub/scm/utils/cpu/mce/mcelog.git;protocol=http;
> file://run-ptest \
> "
>
> -SRCREV = "2cfdf29b2ef98ccd5ed42cdde8bbe437e0d6412f"
> +SRCREV = "2ed5cc0489d20cbffdc6d2e08b1fe49973f0ee34"
>
> LICENSE = "GPLv2"
> -LIC_FILES_CHKSUM = "file://README.md;md5=279840fabb191e6cd9150492d31b0e20"
> +LIC_FILES_CHKSUM = "file://README.md;md5=74bb47b9a68850cb398665cf78b31de6"
>
> S = "${WORKDIR}/git"
>
>
next prev parent reply other threads:[~2018-07-06 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 8:41 [meta-oe][PATCH v2] mcelog: Upgrade to 159 mingli.yu
2018-07-06 8:45 ` Yu, Mingli [this message]
2018-07-06 21:05 ` Khem Raj
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=5B3F2C1B.1050005@windriver.com \
--to=mingli.yu@windriver.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.