mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [APPLIED] grep: add license information
Date: Fri, 24 Nov 2023 08:28:14 +0100	[thread overview]
Message-ID: <20231124072814.1904893-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20231114114807.23620-2-bruno.thomsen@gmail.com>

Thanks, applied as fbe39b9b7d1a2fb941178577019134584c1d9f95.

Michael

[sent from post-receive hook]

On Fri, 24 Nov 2023 08:28:14 +0100, Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> Add license information based on COPYING and web page, including
> license file and hash.
> 
> Licensing from web page[1]:
> 
> Grep is free software; you can redistribute it and/or modify it under the
> terms of the GNU General Public License as published by the Free Software
> Foundation; either version 3 of the License, or (at your option) any later
> version.
> 
> [1] https://www.gnu.org/software/grep/
> 
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> Message-Id: <20231114114807.23620-2-bruno.thomsen@gmail.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/grep.make b/rules/grep.make
> index 7c6280a33368..a1dc4eb716a2 100644
> --- a/rules/grep.make
> +++ b/rules/grep.make
> @@ -15,13 +15,16 @@ PACKAGES-$(PTXCONF_GREP) += grep
>  #
>  # Paths and names
>  #
> -GREP_VERSION	:= 3.8
> -GREP_MD5	:= dc6e4d18d4659e6e7552fc4a183c8ac9
> -GREP		:= grep-$(GREP_VERSION)
> -GREP_SUFFIX	:= tar.xz
> -GREP_URL	:= $(call ptx/mirror, GNU, grep/$(GREP).$(GREP_SUFFIX))
> -GREP_SOURCE	:= $(SRCDIR)/$(GREP).$(GREP_SUFFIX)
> -GREP_DIR	:= $(BUILDDIR)/$(GREP)
> +GREP_VERSION		:= 3.8
> +GREP_MD5		:= dc6e4d18d4659e6e7552fc4a183c8ac9
> +GREP			:= grep-$(GREP_VERSION)
> +GREP_SUFFIX		:= tar.xz
> +GREP_URL		:= $(call ptx/mirror, GNU, grep/$(GREP).$(GREP_SUFFIX))
> +GREP_SOURCE		:= $(SRCDIR)/$(GREP).$(GREP_SUFFIX)
> +GREP_DIR		:= $(BUILDDIR)/$(GREP)
> +GREP_LICENSE		:= GPL-3.0-or-later
> +GREP_LICENSE_FILES	:= \
> +	file://COPYING;md5=1ebbd3e34237af26da5dc08a4e440464
>  
>  # ----------------------------------------------------------------------------
>  # Prepare



  reply	other threads:[~2023-11-24  7:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 11:48 [ptxdist] [PATCH 1/6] gnutls: add license file and hash Bruno Thomsen
2023-11-14 11:48 ` [ptxdist] [PATCH 2/6] grep: add license information Bruno Thomsen
2023-11-24  7:28   ` Michael Olbrich [this message]
2023-11-14 11:48 ` [ptxdist] [PATCH 3/6] htop: add license file and hash Bruno Thomsen
2023-11-24  7:28   ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-14 11:48 ` [ptxdist] [PATCH 4/6] iptables: " Bruno Thomsen
2023-11-24  7:28   ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-14 11:48 ` [ptxdist] [PATCH 5/6] libfastjson: " Bruno Thomsen
2023-11-24  7:28   ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-14 11:48 ` [ptxdist] [PATCH 6/6] json-glib: " Bruno Thomsen
2023-11-24  7:28   ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-24  7:28 ` [ptxdist] [APPLIED] gnutls: " Michael Olbrich
2023-11-24 11:31 ` [ptxdist] [PATCH 1/6] " Roland Hieber
2023-11-27 19:55   ` Bruno Thomsen

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=20231124072814.1904893-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