From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH v2] strace: Version bump. 5.15 -> 5.16
Date: Fri, 4 Feb 2022 19:14:44 +0100 [thread overview]
Message-ID: <20220204181444.GK3897@pengutronix.de> (raw)
In-Reply-To: <6bcbeb8b-3bce-dbda-3a4c-003621e9ae07@t2data.com>
Hi,
On Fri, Feb 04, 2022 at 06:44:45PM +0100, Christian Melki wrote:
> Bump. Didn't make it to the release.
> Anything broken that needs fixing?
I missed the new version last week and I usually don't merge any new
patches in the week of the release. Just bugfixes for regressions that show
up during testing and stuff like that.
I've picked it up after the release for initial testing and it's merged
now.
Michael
> On 1/28/22 11:34, Christian Melki wrote:
> > Mostly bugfixes.
> > Copyright year number range updated in COPYING file.
> > https://strace.io/files/5.16/
> >
> > Signed-off-by: Christian Melki <christian.melki@t2data.com>
> > ---
> > rules/strace.make | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/rules/strace.make b/rules/strace.make
> > index aa13f3e97..aeec39aa6 100644
> > --- a/rules/strace.make
> > +++ b/rules/strace.make
> > @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_STRACE) += strace
> > #
> > # Paths and names
> > #
> > -STRACE_VERSION := 5.15
> > -STRACE_MD5 := a627c23fda3ecd668d6161c288fdcd79
> > +STRACE_VERSION := 5.16
> > +STRACE_MD5 := f848d24b2371948c91b57f72c0e75e66
> > STRACE := strace-$(STRACE_VERSION)
> > STRACE_SUFFIX := tar.xz
> > STRACE_URL := https://strace.io/files/$(STRACE_VERSION)/$(STRACE).$(STRACE_SUFFIX)
> > @@ -25,7 +25,7 @@ STRACE_SOURCE := $(SRCDIR)/$(STRACE).$(STRACE_SUFFIX)
> > STRACE_DIR := $(BUILDDIR)/$(STRACE)
> > STRACE_LICENSE := LGPL-2.1-or-later AND GPL-2.0-only WITH Linux-syscall-note
> > STRACE_LICENSE_FILES := \
> > - file://COPYING;md5=318cfc887fc8723f4e9d4709b55e065b \
> > + file://COPYING;md5=59a33f0a3e6122d67c0b3befccbdaa6b \
> > file://bundled/linux/COPYING;md5=391c7a5bbfb151ad3dbe0a7fb5791a46 \
> > file://bundled/linux/GPL-2.0;md5=e6a75371ba4d16749254a51215d13f97 \
> > file://LGPL-2.1-or-later;md5=9e4c7a7a5be83d7f3da645ac5d466052
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2022-02-04 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 10:34 Christian Melki
2022-02-04 17:44 ` Christian Melki
2022-02-04 18:14 ` Michael Olbrich [this message]
2022-02-04 18:08 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20220204181444.GK3897@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