From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [APPLIED] libestr: add license file and hash
Date: Tue, 28 Nov 2023 09:36:35 +0100 [thread overview]
Message-ID: <20231128083635.1031456-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20231119200819.38425-1-bruno.thomsen@gmail.com>
Thanks, applied as b9d8977bcafaa2a434275d4d9dc28da008f3a79d.
Michael
[sent from post-receive hook]
On Tue, 28 Nov 2023 09:36:35 +0100, Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> Message-Id: <20231119200819.38425-1-bruno.thomsen@gmail.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libestr.make b/rules/libestr.make
> index ea2c572d1670..10e32f19bd83 100644
> --- a/rules/libestr.make
> +++ b/rules/libestr.make
> @@ -14,14 +14,16 @@ PACKAGES-$(PTXCONF_LIBESTR) += libestr
> #
> # Paths and names
> #
> -LIBESTR_VERSION := 0.1.10
> -LIBESTR_MD5 := f4c9165a23587e77f7efe65d676d5e8e
> -LIBESTR := libestr-$(LIBESTR_VERSION)
> -LIBESTR_SUFFIX := tar.gz
> -LIBESTR_URL := http://libestr.adiscon.com/files/download/$(LIBESTR).$(LIBESTR_SUFFIX)
> -LIBESTR_SOURCE := $(SRCDIR)/$(LIBESTR).$(LIBESTR_SUFFIX)
> -LIBESTR_DIR := $(BUILDDIR)/$(LIBESTR)
> -LIBESTR_LICENSE := LGPL-2.1-or-later
> +LIBESTR_VERSION := 0.1.10
> +LIBESTR_MD5 := f4c9165a23587e77f7efe65d676d5e8e
> +LIBESTR := libestr-$(LIBESTR_VERSION)
> +LIBESTR_SUFFIX := tar.gz
> +LIBESTR_URL := http://libestr.adiscon.com/files/download/$(LIBESTR).$(LIBESTR_SUFFIX)
> +LIBESTR_SOURCE := $(SRCDIR)/$(LIBESTR).$(LIBESTR_SUFFIX)
> +LIBESTR_DIR := $(BUILDDIR)/$(LIBESTR)
> +LIBESTR_LICENSE := LGPL-2.1-or-later
> +LIBESTR_LICENSE_FILES := \
> + file://COPYING;md5=9d6c993486c18262afba4ca5bcb894d0
>
> # ----------------------------------------------------------------------------
> # Prepare
prev parent reply other threads:[~2023-11-28 8:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 20:08 [ptxdist] [PATCH 1/8] " Bruno Thomsen
2023-11-19 20:08 ` [ptxdist] [PATCH 2/8] libffi: " Bruno Thomsen
2023-11-28 8:36 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-19 20:08 ` [ptxdist] [PATCH 3/8] libmbim: " Bruno Thomsen
2023-11-28 8:36 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-19 20:08 ` [ptxdist] [PATCH 4/8] libndp: " Bruno Thomsen
2023-11-28 8:36 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-19 20:08 ` [ptxdist] [PATCH 5/8] libp11: " Bruno Thomsen
2023-11-28 8:36 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-19 20:08 ` [ptxdist] [PATCH 6/8] libseccomp: " Bruno Thomsen
2023-11-28 8:36 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-19 20:08 ` [ptxdist] [PATCH 7/8] p11-kit: " Bruno Thomsen
2023-11-28 8:36 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-19 20:08 ` [ptxdist] [PATCH 8/8] python3-ply: update license Bruno Thomsen
2023-11-28 8:36 ` Michael Olbrich [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=20231128083635.1031456-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=bruno.thomsen@gmail.com \
--cc=ptxdist@pengutronix.de \
/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