public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Mark Wielaard <mark@klomp.org>, dwz@sourceware.org
Subject: Re: DWZ maintainance
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <e64a48d7-a6d2-0b43-6306-a6c71fa63dd8@suse.de> (raw)
In-Reply-To: <20190617152609.GT19695@tucnak>

On 17-06-19 17:26, Jakub Jelinek wrote:
> Hi!
> 
> 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.

Hi Jakub,

thanks, I'm definitely OK with that :)

> Once sufficient amount of changes is in, would be nice to roll a new release.

OK, makes sense.

Thanks,
- Tom

  reply	other threads:[~2019-06-17 15:55 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 [this message]
2019-01-01  0:00   ` Mark Wielaard
2019-01-01  0:00     ` Tom de Vries

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=e64a48d7-a6d2-0b43-6306-a6c71fa63dd8@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).