From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Re: elfutils 0.189 release next week
Date: Thu, 02 Mar 2023 12:36:15 +0100 [thread overview]
Message-ID: <2d66c4922c67df6017c9f83c97e8bf72ba67f995.camel@klomp.org> (raw)
In-Reply-To: <1996fa4b82dc285843621a3cd901fe687f0396c7.camel@klomp.org>
Hi,
On Tue, 2023-02-21 at 14:33 +0100, Mark Wielaard wrote:
> We accumulated a lot of patches since 0.188 (59 commits by 13 authors)
> with some nice new features and some important bug fixes. So it would
> be good to push a new release out.
>
> I cleaned up the patchwork list and will go over the following 25
> pending patches to see what can be incorporated:
> https://patchwork.sourceware.org/project/elfutils/list/ [*]
> If your patch is not on that list please ping.
>
> I propose to do the 0.189 release on Tuesday February 28, but it can be
> earlier or later if that is more convenient.
I still would like to do a release this week (so tomorrow, Friday). We
made good progress on the patch queue. Only 4 are still marked as NEW
and 6 more patches made it in. Please go over the review notes of any
patches you really want to go in before the release. We'll do another
one in 3 months, so don't feel pressured.
I am still looking at the "A scenario where Perf cannot unwind the user
stack by dwarf with libdw.so" patch [1]. It cannot be replicated with
eu-stack, which surprises me, so perf and eu-stack do something
different and I don't yet understand what that is.
Cheers,
Mark
[1]
https://patchwork.sourceware.org/project/elfutils/patch/88c25e0709834e1a816630c944377640@huawei.com/
(But most discussion has been off-list)
prev parent reply other threads:[~2023-03-02 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 13:33 Mark Wielaard
2023-03-02 11:36 ` Mark Wielaard [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=2d66c4922c67df6017c9f83c97e8bf72ba67f995.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).