mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libtasn1: Version bump. 4.17.0 -> 4.18.0
Date: Fri,  8 Apr 2022 15:36:03 +0200	[thread overview]
Message-ID: <20220408133603.123170-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220404125340.4135496-1-christian.melki@t2data.com>

Thanks, applied as 59b4dff5c040bb89703c0ae8f7c112fac41c94f9.

Michael

[sent from post-receive hook]

On Fri, 08 Apr 2022 15:36:02 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Minimal changes.
> https://github.com/gnutls/libtasn1/blob/master/NEWS
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20220404125340.4135496-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/libtasn1.make b/rules/libtasn1.make
> index cd6a504c30c9..7e54635d2e92 100644
> --- a/rules/libtasn1.make
> +++ b/rules/libtasn1.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBTASN1) += libtasn1
>  #
>  # Paths and names
>  #
> -LIBTASN1_VERSION	:= 4.17.0
> -LIBTASN1_MD5		:= c46f6eb3bd1287031ae5d36465094402
> +LIBTASN1_VERSION	:= 4.18.0
> +LIBTASN1_MD5		:= 8203e72a2c0390515410b2ea2c032f04
>  LIBTASN1		:= libtasn1-$(LIBTASN1_VERSION)
>  LIBTASN1_SUFFIX		:= tar.gz
>  LIBTASN1_URL		:= $(call ptx/mirror, GNU, libtasn1/$(LIBTASN1).$(LIBTASN1_SUFFIX))

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


      parent reply	other threads:[~2022-04-08 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 12:53 [ptxdist] [PATCH] " Christian Melki
2022-04-04 12:53 ` [ptxdist] [PATCH] gnutls: Version bump. 3.7.3 -> 3.7.4 Christian Melki
2022-04-08  9:05   ` Michael Olbrich
2022-04-08 13: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=20220408133603.123170-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.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