From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/mender: bump to version 2.0.0
Date: Sun, 26 May 2019 20:55:10 +0200 [thread overview]
Message-ID: <20190526205510.04cc44ea@windsurf> (raw)
In-Reply-To: <20190508154924.67828-1-aduskett@gmail.com>
Hello Adam,
On Wed, 8 May 2019 11:49:24 -0400
aduskett at gmail.com wrote:
> From: Adam Duskett <Aduskett@gmail.com>
>
> In addition:
> - Update hashes for license files.
As we have already explain a zillion times already, when the license
hashes are changed, there *must* be an explanation in the commit log
about what changed in the license file(s).
> diff --git a/package/mender/Config.in b/package/mender/Config.in
> index 5ab2304e49..e8c29bb33e 100644
> --- a/package/mender/Config.in
> +++ b/package/mender/Config.in
> @@ -3,6 +3,7 @@ config BR2_PACKAGE_MENDER
> depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
> depends on BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
> depends on BR2_TOOLCHAIN_HAS_THREADS
> + select BR2_PACKAGE_XZ # LZMA
The "LZMA" comment is not necessary, we typically don't have such
comments.
Could you resend with an updated commit log that explains the license
file changes ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-05-26 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 15:49 [Buildroot] [PATCH 1/1] package/mender: bump to version 2.0.0 aduskett at gmail.com
2019-05-26 18:55 ` Thomas Petazzoni [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=20190526205510.04cc44ea@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.