mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] c-ares: fix license files variable name
Date: Fri, 17 Feb 2023 16:35:44 +0100	[thread overview]
Message-ID: <20230217153544.1253745-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230213093117.1865063-1-rhi@pengutronix.de>

Thanks, applied as fd5da21491dd93db75c41222c0ddf89a05c3996b.

Michael

[sent from post-receive hook]

On Fri, 17 Feb 2023 16:35:43 +0100, Roland Hieber <rhi@pengutronix.de> wrote:
> The variable name did nothing, but LICENSE was auto-detected anyway. Now
> this just pins down the MD5.
> 
> Fixes: d3e729ff2c2a12a834c8 (2018-05-30, "c-ares: version bump 1.10.0 -> 1.14.0")
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> Message-Id: <20230213093117.1865063-1-rhi@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/c-ares.make b/rules/c-ares.make
> index 7a0dd3175349..26ebf0897ee8 100644
> --- a/rules/c-ares.make
> +++ b/rules/c-ares.make
> @@ -22,7 +22,7 @@ C_ARES_URL	:= http://c-ares.haxx.se/download/$(C_ARES).$(C_ARES_SUFFIX)
>  C_ARES_SOURCE	:= $(SRCDIR)/$(C_ARES).$(C_ARES_SUFFIX)
>  C_ARES_DIR	:= $(BUILDDIR)/$(C_ARES)
>  C_ARES_LICENSE	:= MIT
> -C_ARES_LICENSE_MD5	:= file://LICENSE.md;md5=fb997454c8d62aa6a47f07a8cd48b006
> +C_ARES_LICENSE_FILES	:= file://LICENSE.md;md5=fb997454c8d62aa6a47f07a8cd48b006
>  
>  
>  # ----------------------------------------------------------------------------



      parent reply	other threads:[~2023-02-17 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  9:31 [ptxdist] [PATCH 1/2] " Roland Hieber
2023-02-13  9:31 ` [ptxdist] [PATCH 2/2] open62541: version bump 1.2 -> 1.3.4 Roland Hieber
2023-02-17 15:35   ` [ptxdist] [APPLIED] " Michael Olbrich
2023-02-17 15:35 ` 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=20230217153544.1253745-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=rhi@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