From: Di Chen <dichen@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org
Subject: Re: Proposing elfutils-0.187 for Monday 25 April
Date: Fri, 15 Apr 2022 19:51:46 +0800 [thread overview]
Message-ID: <CAN-Pu7T40cMAYjpLKP8t_qxkpU1T-xXuxN9giVt=jKFLSawB-w@mail.gmail.com> (raw)
In-Reply-To: <95e2503a1cc016eb340020e3f73a825a25f05b41.camel@klomp.org>
Hey Mark,
The latest patch for PR28928 locates in bugzilla, and it's attached in
https://sourceware.org/bugzilla/show_bug.cgi?id=28928
Di
On Fri, Apr 15, 2022 at 6:41 PM Mark Wielaard <mark@klomp.org> wrote:
> Hi,
>
> It has been 5 months since elfutils 0.186 was released. There have been
> more than 70 commits since then. And 20 bugs closed.
>
> I propose we do an elfutils 0.187 release Monday 25 April.
>
> There are still a couple of unreviewed patches:
> https://patchwork.sourceware.org/project/elfutils/list/
> I'll try to go over them all before the release.
>
> If there are any other issues left, please let me know.
>
> Lets try to do the next release in 3 months, so there isn't such a big
> gap between releases.
>
> Cheers,
>
> Mark
>
>
prev parent reply other threads:[~2022-04-15 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 10:40 Mark Wielaard
2022-04-15 11:51 ` Di Chen [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='CAN-Pu7T40cMAYjpLKP8t_qxkpU1T-xXuxN9giVt=jKFLSawB-w@mail.gmail.com' \
--to=dichen@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.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).