public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Doing an October Surprise 0.182 release
Date: Fri, 30 Oct 2020 15:19:00 +0100	[thread overview]
Message-ID: <e6d1ba13b901603e7a32ca16f53dcab5be39ace8.camel@klomp.org> (raw)

Hi all,

Once the latest debuginfod patches and the valgrind make check patch
are in I would like to do a new release. It has only been 2 months
since 0.181, and there have only been ~25 commits since then, but there
are a couple of important (IMHO) bug fixes, specifically the
read_ubyte3_unaligned and sleb128 reading fixes (which have been in the
code for some while, but they are important to get right now that we
are seeing more DWARF5). There are also some new features that are
important to handle newer kernels, like the zstd support and having
debuginfod-find handle compressed (kernel) ELF images. Plus the
cleanups to debuginfod to make it index more efficiently.

I'll try to spin the release this weekend or on Monday at the latest
(although then it wouldn't be an October Surprise anymore :)

Cheers,

Mark

                 reply	other threads:[~2020-10-30 14:19 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=e6d1ba13b901603e7a32ca16f53dcab5be39ace8.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).