From: Mark Wielaard <mark@klomp.org>
To: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Proposed elfutils 0.188 release in Wednesday
Date: Mon, 31 Oct 2022 12:15:34 +0100 [thread overview]
Message-ID: <abaedf97edf7057c33e665b070ca074a66b3b71c.camel@klomp.org> (raw)
Hi,
It has been 6 months since 0.187. There have been almost 80 commits
since, various bug fixes and some new features (see NEWS). I would like
to push out a 0.188 this Wednesday (Nov 2). Please go over any open
bugs or patches to see if they should be fixed/committed before the
release or can wait for the next release (lets do 0.189 in 3 months,
end of January, as we normally do, instead of waiting 6 months).
Cheers,
Mark
reply other threads:[~2022-10-31 11:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=abaedf97edf7057c33e665b070ca074a66b3b71c.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).