mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] strace: Version bump. 6.6 -> 6.7
Date: Fri, 2 Feb 2024 13:22:01 +0100	[thread overview]
Message-ID: <ZbzeaRKlSnXsw1sE@pengutronix.de> (raw)
In-Reply-To: <Zbzdxl8Ps6938glG@pengutronix.de>

On Fri, Feb 02, 2024 at 01:19:18PM +0100, Michael Olbrich wrote:
> On Wed, Jan 31, 2024 at 07:04:09PM +0100, Christian Melki wrote:
> > Minor fixes and enhancements.
> > https://github.com/strace/strace/releases/tag/v6.7
> > 
> > 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 f61fdecea..2b505e57e 100644
> > --- a/rules/strace.make
> > +++ b/rules/strace.make
> > @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_STRACE) += strace
> >  #
> >  # Paths and names
> >  #
> > -STRACE_VERSION	:= 6.6
> > -STRACE_MD5	:= e1e791635e89113a78e889bfe070c111
> > +STRACE_VERSION	:= 6.7
> > +STRACE_MD5	:= 8eb0aa75111a8e66cc14176159cc8ee9
> >  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=63c8c3eb5c71b4362edac1397f40bdc7 \
> > +	file://COPYING;md5=2433d82e1432a76dc3eadd9002bfe304\
> 
> What changed in this file?

Never mind. I should look at all the mails before replying. I just saw v2
with the extended commit message.

Michael

> >  	file://bundled/linux/COPYING;md5=391c7a5bbfb151ad3dbe0a7fb5791a46 \
> >  	file://bundled/linux/GPL-2.0;md5=e6a75371ba4d16749254a51215d13f97 \
> >  	file://LGPL-2.1-or-later;md5=9e4c7a7a5be83d7f3da645ac5d466052
> > -- 
> > 2.34.1
> > 
> > 
> > 
> 
> -- 
> 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 |
> 
> 

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



      reply	other threads:[~2024-02-02 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 18:04 Christian Melki
2024-02-02 12:19 ` Michael Olbrich
2024-02-02 12:22   ` 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=ZbzeaRKlSnXsw1sE@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