From: Tom de Vries <tdevries@suse.de>
To: Mark Wielaard <mark@klomp.org>, Jakub Jelinek <jakub@redhat.com>
Cc: dwz@sourceware.org
Subject: Re: DWZ maintainance
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <02ba4ac9-e1d2-30fe-3bb2-662d8b9c76f2@suse.de> (raw)
In-Reply-To: <f2c41161d05d8226007ce1d2a647ef0448cbdd33.camel@klomp.org>
On 18-06-19 10:37, Mark Wielaard wrote:
> On Mon, 2019-06-17 at 17:54 +0200, Tom de Vries wrote:
>> On 17-06-19 17:26, Jakub Jelinek wrote:
>>> I thought I'd have some time to do dwz patch review and maintainance,
>>> but apparently I don't, my GCC duties are full time.
>>> So, I'd like to declare Tom as a co-maintainer if he is ok with that,
>>> as I don't want to block progress.
>>
>> thanks, I'm definitely OK with that :)
>
> Great. Also my apologies for not having more time for dwz. But I am
> around to help (and keep the buildbot alive).
>
Much appreciated :)
>>> Once sufficient amount of changes is in, would be nice to roll a
>>> new release.
>>
>> OK, makes sense.
>
> IMHO you could do a release now. There are a couple of bug fixes in
> already since 0.12. Which I would say is certainly "sufficient" to
> warrant a release (otherwise distros would have to backport them). And
> it would show that dwz is alive and well :)
I hope to spent next week (i.e. hackweek) in full on dwz, and to be able
to push a couple of more fixes.
In particular, I'd like to commit fixes for:
- PR24249 - "Section offsets not monotonically increasing"
- PR24251 - "Allocatable section after non-allocatable ones"
which will mean that I can drop this (
https://build.opensuse.org/package/view_file/openSUSE:Factory/dwz/dwz-0.12-ignore-nobits.patch?expand=1
) patch when upgrading to the next dwz release.
Thanks,
- Tom
prev parent reply other threads:[~2019-06-18 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Jakub Jelinek
2019-01-01 0:00 ` Tom de Vries
2019-01-01 0:00 ` Mark Wielaard
2019-01-01 0:00 ` Tom de Vries [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=02ba4ac9-e1d2-30fe-3bb2-662d8b9c76f2@suse.de \
--to=tdevries@suse.de \
--cc=dwz@sourceware.org \
--cc=jakub@redhat.com \
--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).