From: Georg-Johann Lay <avr@gjlay.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Gerald Pfeifer <gerald@pfeifer.com>, Jeff Law <law@redhat.com>,
gcc-patches@gcc.gnu.org
Subject: Re: AVR maintainership
Date: Fri, 18 Dec 2020 17:53:16 +0100 [thread overview]
Message-ID: <5FDCDE7C.1070800@gjlay.de> (raw)
In-Reply-To: <20201215143031.GC2672@gate.crashing.org>
Segher Boessenkool schrieb:
> On Tue, Dec 15, 2020 at 08:40:08AM +0100, Gerald Pfeifer wrote:
>> On Mon, 6 Jan 2020, Jeff Law wrote:
>>>> p.s. You know anything about Denis Chertykov? He used to reply to avr
>>>> patches within hours, but my latest patches (after a long period where I
>>>> didn't propose any patches) where all approved by you; not a single mail
>>>> from Denis. So I am concerned if he's well. Maybe he left you or some
>>>> other global maintainer a note? He's still listed as maintainer though.
>>> I haven't heard much from him for a while. I'm trying to leave enough
>>> space that he can step in on this stuff, but I'm also hesitant to let
>>> patches linger for too long.
>> I don't think I have seen mails from Denis since then (more than
>> eleven months).
>>
>> Do we need to get a new maintainer for AVR in place? Any nominations?
>
> I nominate Georg-Johann Lay as the obvious choice, since he has authored
> 333 of the 511 patches that went into config/avr/ the last ten years.
>
>
> Segher
Thanks, I feel honoured by this proposal.
However, I have to decline it and cannot set in as avr maintainer
because I do not have respective resources right now.
Johann
next prev parent reply other threads:[~2020-12-18 16:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 16:43 [patch,avr, 0/3] Support 64-bit (long) double Georg-Johann Lay
2019-12-16 16:46 ` [patch,avr, 1/3] Support 64-bit (long) double: The gcc part Georg-Johann Lay
2019-12-28 13:20 ` [PING^1][patch,avr, " Georg-Johann Lay
2020-01-06 13:08 ` [Ping^2][patch,avr, " Georg-Johann Lay
2020-01-06 16:25 ` [patch,avr, " Jeff Law
2020-01-06 17:10 ` Georg-Johann Lay
2020-01-06 17:16 ` Jeff Law
2020-12-15 7:40 ` AVR maintainership (was: [patch,avr, 1/3] Support 64-bit (long) double: The gcc part.) Gerald Pfeifer
2020-12-15 14:30 ` AVR maintainership (was: [patch, avr, " Segher Boessenkool
2020-12-15 20:42 ` AVR maintainership (was: [patch,avr, " Jeff Law
2020-12-18 16:53 ` Georg-Johann Lay [this message]
2019-12-16 16:49 ` [patch,avr, 2/3] Support 64-bit (long) double: The libgcc changes Georg-Johann Lay
2019-12-28 12:00 ` [PING^1][patch,avr, " Georg-Johann Lay
2020-01-06 13:08 ` [Ping^2][patch,avr, " Georg-Johann Lay
2020-01-06 16:26 ` [patch,avr, " Jeff Law
2019-12-16 17:09 ` [patch,avr, 3/3] Support 64-bit (long) double: libf7 Georg-Johann Lay
2019-12-28 12:02 ` [PING^1][patch,avr, " Georg-Johann Lay
2020-01-06 13:09 ` [Ping^2][patch,avr, " Georg-Johann Lay
2020-01-06 16:26 ` [patch,avr, " Jeff Law
2019-12-28 11:59 ` [PING^1][patch,avr, 0/3] Support 64-bit (long) double Georg-Johann Lay
2019-12-28 11:59 ` Georg-Johann Lay
2020-01-06 13:08 ` [Ping^2][patch,avr, " Georg-Johann Lay
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=5FDCDE7C.1070800@gjlay.de \
--to=avr@gjlay.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=law@redhat.com \
--cc=segher@kernel.crashing.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).