public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Development <gcc@gcc.gnu.org>, David Edelsohn <edelsohn@gnu.org>
Subject: Re: Stepping down as gcov maintainer and callgraph reviewer
Date: Thu, 16 Feb 2023 20:46:26 +0100	[thread overview]
Message-ID: <Y+6IEiSvOC43ZfEY@kam.mff.cuni.cz> (raw)
In-Reply-To: <8ec0a414-a5e2-59ed-9f6f-cc7556af9a16@suse.cz>

Martin,
> 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 am sad to hear this news and will definitely miss you as coleague
and co-maintaner.  Thank you for all the work on GCC!

Honza
> 
> I wish the project all the best!
> 
> Cheers,
> Martin

> From bb3aee20cdeeb6399ca77ac05cd8093d66256df3 Mon Sep 17 00:00:00 2001
> From: Martin Liska <mliska@suse.cz>
> Date: Thu, 16 Feb 2023 16:50:38 +0100
> Subject: [PATCH] MAINTAINERS: stepping down from my positions
> 
> ChangeLog:
> 
> 	* MAINTAINERS: I'm stepping down from my positions.
> ---
>  MAINTAINERS | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 18edc86df67..a61d3ae06df 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -230,7 +230,6 @@ docstring relicensing	Gerald Pfeifer		<gerald@pfeifer.com>
>  docstring relicensing	Joseph Myers		<joseph@codesourcery.com>
>  predict.def		Jan Hubicka		<hubicka@ucw.cz>
>  gcov			Jan Hubicka		<hubicka@ucw.cz>
> -gcov			Martin Liska		<mliska@suse.cz>
>  gcov			Nathan Sidwell		<nathan@acm.org>
>  option handling		Joseph Myers		<joseph@codesourcery.com>
>  middle-end		Jeff Law		<jeffreyalaw@gmail.com>
> @@ -268,7 +267,6 @@ check in changes outside of the parts of the compiler they maintain.
>  			Reviewers
>  
>  arc port		Claudiu Zissulescu	<claziss@synopsys.com>
> -callgraph		Martin Liska		<mliska@suse.cz>
>  callgraph		Martin Jambor		<mjambor@suse.cz>
>  C front end		Marek Polacek		<polacek@redhat.com>
>  CTF, BTF		David Faust		<david.faust@oracle.com>
> @@ -519,6 +517,7 @@ Kriang Lerdsuwanakij				<lerdsuwa@users.sourceforge.net>
>  Renlin Li					<renlin.li@arm.com>
>  Xinliang David Li				<davidxl@google.com>
>  Chen Liqin					<liqin.gcc@gmail.com>
> +Martin Liska					<mliska@suse.cz>
>  Jiangning Liu					<jiangning.liu@arm.com>
>  Sa Liu						<saliu@de.ibm.com>
>  Ralph Loader					<rcl@ihug.co.nz>
> -- 
> 2.39.1
> 


  parent reply	other threads:[~2023-02-16 19:46 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
2023-02-16 16:09 ` Mark Wielaard
2023-02-16 19:46 ` Jan Hubicka [this message]
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=Y+6IEiSvOC43ZfEY@kam.mff.cuni.cz \
    --to=hubicka@ucw.cz \
    --cc=edelsohn@gnu.org \
    --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).