public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@arm.com>
To: Dimitrije Milosevic <Dimitrije.Milosevic@Syrmia.com>
Cc: Xi Ruoyao <xry111@xry111.site>,
	"gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Djordje Todorovic <Djordje.Todorovic@syrmia.com>
Subject: Re: PING: [PATCH] libsanitizer: Cherry-pick 2bfb0fcb51510f22723c8cdfefe from upstream
Date: Wed, 27 Jul 2022 13:57:38 +0100	[thread overview]
Message-ID: <mptilniu30d.fsf@arm.com> (raw)
In-Reply-To: <AM0PR03MB488286D8928480460471331682979@AM0PR03MB4882.eurprd03.prod.outlook.com> (Dimitrije Milosevic's message of "Wed, 27 Jul 2022 06:52:26 +0000")

Dimitrije Milosevic <Dimitrije.Milosevic@Syrmia.com> writes:
>> Do you know someone very familiar with MIPS and GCC and capable as a
>> port maintainer?  An active MIPS port maintainer will make the situation
>> better.
> Sadly, no. I agree it would make things easier.

Yeah, I agree that's what we need.  I stepped down from being a MIPS
maintainer over eight years ago and Matthew moved on to other things
several years ago as well.  The port has been unmaintained for a long
time now.

For a while I tried to be practical and approve trivial patches, even
though working for an IP company makes that somewhat awkward from a
conflict-of-interest perspective.  But it's been so long now since
I worked on MIPS that the technical side is becoming a problem too.

Thanks,
Richard

  reply	other threads:[~2022-07-27 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25  6:55 Dimitrije Milosevic
2022-07-25  7:04 ` Xi Ruoyao
2022-07-27  6:41 ` PING: " Dimitrije Milosevic
2022-07-27  6:43   ` Xi Ruoyao
2022-07-27  6:52     ` Dimitrije Milosevic
2022-07-27 12:57       ` Richard Sandiford [this message]
2022-07-28 13:43 ` Dimitrije Milosevic
2022-07-28 13:48   ` Martin Liška
2022-07-29  6:38     ` Dimitrije Milosevic
2022-08-01  4:11       ` Martin Liška

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=mptilniu30d.fsf@arm.com \
    --to=richard.sandiford@arm.com \
    --cc=Dimitrije.Milosevic@Syrmia.com \
    --cc=Djordje.Todorovic@syrmia.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=xry111@xry111.site \
    /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).