public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Stepping down as gcov maintainer and callgraph reviewer
Date: Thu, 16 Feb 2023 11:08:31 -0500	[thread overview]
Message-ID: <CAGWvnyn6Db=k4bfV4FVXLCXQXOvFPzq=z7ix8Bfnfdo6H5thzQ@mail.gmail.com> (raw)
In-Reply-To: <8ec0a414-a5e2-59ed-9f6f-cc7556af9a16@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

On Thu, Feb 16, 2023 at 10:54 AM Martin Liška <mliska@suse.cz> wrote:

> Hello GCC community.
>
> After spending last decade (including my diploma thesis even more)
> of my life working on GCC, I decided to leave the project and try
> a different job. I would like to thank all the community members I had
> change to interact with, I learned so much and enjoyed the journey!
> I'll be leaving somewhen at the beginning of May.
>
> That said, I'm stepping down from my 2 positions as I won't have a time
> for proper patch review and bugs in the area I'm responsible for.
>
> I wish the project all the best!
>

Hi, Martin

Thank you very much for your great work on GCC over the past years.  Your
excellent technical contributions to GCC and to the development environment
behind the scenes have helped create and maintain a world-class toolchain
that powers the world.

Wishing you much success in the next steps of your career and I eagerly
await to see the tremendous impact where you choose to apply your skills
next.

Thanks, David

  reply	other threads:[~2023-02-16 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 15:54 Martin Liška
2023-02-16 16:08 ` David Edelsohn [this message]
2023-02-16 16:09 ` Mark Wielaard
2023-02-16 19:46 ` Jan Hubicka
2023-03-07 14:42   ` Martin Liška
2023-02-17 16:18 ` Aldy Hernandez
2023-02-17 19:51   ` Jeff Law

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='CAGWvnyn6Db=k4bfV4FVXLCXQXOvFPzq=z7ix8Bfnfdo6H5thzQ@mail.gmail.com' \
    --to=dje.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mliska@suse.cz \
    /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).