From: Ladislav Michl <oss-lists@triops.cz>
To: Christian Melki <christian.melki@t2data.com>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] libunwind: Version bump. 1.70 -> 1.7.1
Date: Tue, 25 Jul 2023 06:58:54 +0200 [thread overview]
Message-ID: <ZL9WjnyYHMCnb+zA@lenoch> (raw)
In-Reply-To: <81087ebc-3e2c-82db-bd98-0a6617effc4c@t2data.com>
On Mon, Jul 24, 2023 at 08:32:36PM +0200, Christian Melki wrote:
> On 7/24/23 19:04, Ladislav Michl wrote:
> > Hi,
> >
> > On Mon, Jul 24, 2023 at 05:58:15PM +0200, Christian Melki wrote:
> >> Developers fixed the tarball misnomer and released a new version.
> >> No other changes.
> >>
> >> * (Re-)fix URL and remove comment.
> >
>
> Normally you'd be right, but not this time around. :)
> They broke the tarball and version name,
> hence the comment above and the nag in the previous bump commit.
>
> https://github.com/libunwind/libunwind/releases/tag/v1.7.1
> https://github.com/libunwind/libunwind/compare/v1.7.0...v1.7.1
>
> https://github.com/libunwind/libunwind/issues/535
Well, the previous commit was:
libunwind: Version bump. 1.6.2 -> 1.7.0 (-ish).
So I would expect this one is following the same scheme, otherwise it
is hard to tell what's happening without reading both commit messages.
Unless this is meant as developer attention test ;-)
> > note small typo in the subject: 1.70 -> 1.7.0
> >
> > l.
> >
next prev parent reply other threads:[~2023-07-25 4:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 15:58 Christian Melki
2023-07-24 17:04 ` Ladislav Michl
2023-07-24 18:32 ` Christian Melki
2023-07-25 4:58 ` Ladislav Michl [this message]
2023-08-01 7:48 ` [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=ZL9WjnyYHMCnb+zA@lenoch \
--to=oss-lists@triops.cz \
--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