public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <jsm@polyomino.org.uk>
To: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: [committed] MAINTAINERS: Update my email address
Date: Sat, 30 Dec 2023 00:32:42 +0000 (UTC)	[thread overview]
Message-ID: <e623545c-654d-48b4-1b53-54212664b2f@polyomino.org.uk> (raw)

There will be another update in January.

diff --git a/binutils/MAINTAINERS b/binutils/MAINTAINERS
index fc2d421bd16..0894a56a873 100644
--- a/binutils/MAINTAINERS
+++ b/binutils/MAINTAINERS
@@ -140,7 +140,7 @@ responsibility among the other maintainers.
   SPARC		   Jose E. Marchesi <jose.marchesi@oracle.com>
   SPU		   Alan Modra <amodra@gmail.com>
   TIC54X           Timothy Wall <twall@alum.mit.edu>
-  TIC6X            Joseph Myers <joseph@codesourcery.com>
+  TIC6X            Joseph Myers <jsm@polyomino.org.uk>
   TILE-Gx          Walter Lee <walt@tilera.com>
   TILEPro          Walter Lee <walt@tilera.com>
   VAX		   Matt Thomas <matt@netbsd.org>
diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS
index ca2eaea6068..f57e616b58f 100644
--- a/gdb/MAINTAINERS
+++ b/gdb/MAINTAINERS
@@ -688,7 +688,7 @@ Phil Muldoon					pmuldoon@redhat.com
 Pierre Muller					muller@sourceware.org
 Gaius Mulley					gaius@glam.ac.uk
 Masaki Muranaka					monaka@monami-software.com
-Joseph Myers					joseph@codesourcery.com
+Joseph Myers					jsm@polyomino.org.uk
 Fernando Nasser					fnasser@redhat.com
 Adam Nemet					anemet@caviumnetworks.com
 Will Newton					will.newton@linaro.org

-- 
Joseph S. Myers
jsm@polyomino.org.uk

             reply	other threads:[~2023-12-30  0:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30  0:32 Joseph Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-08 18:55 Joseph Myers
2015-10-08 18:12 Maciej W. Rozycki

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=e623545c-654d-48b4-1b53-54212664b2f@polyomino.org.uk \
    --to=jsm@polyomino.org.uk \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.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).