public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@codesourcery.com>
To: gcc-patches@gcc.gnu.org
Subject: update email address
Date: Mon, 27 Apr 2009 20:11:00 -0000	[thread overview]
Message-ID: <1240862062.3278.70.camel@localhost.localdomain> (raw)

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

I'm still doing the same Cisco work that I've been doing for nearly 3
years now, but now I'm doing it for CodeSourcery.  The new contract
finally allows me to contribute patches that I write at Cisco, which is
something that Cygnus/Red Hat/Specifix/CodeSourcery have been trying to
get for about 15 years.  It is nice to have this finally resolved.  

I have checked in a patch to update my email address in the MAINTAINERS
file.

Jim


[-- Attachment #2: maint.patch --]
[-- Type: text/x-patch, Size: 1981 bytes --]

2009-04-27  James E. Wilson  <wilson@codesourcery.com>

	* MAINTAINERS: Update my e-mail address.

Index: MAINTAINERS
===================================================================
--- MAINTAINERS	(revision 146849)
+++ MAINTAINERS	(working copy)
@@ -32,7 +32,7 @@ Mark Mitchell					mark@codesourcery.com
 Diego Novillo					dnovillo@google.com
 Bernd Schmidt					bernd.schmidt@analog.com
 Ian Lance Taylor				ian@airs.com
-Jim Wilson					wilson@tuliptree.org
+Jim Wilson					wilson@codesourcery.com
 
 Note that while global reviewers can approve changes to any part of
 the compiler or associated libraries, they still need approval for
@@ -59,7 +59,7 @@ hppa port		John David Anglin	dave.anglin
 i386 port		Richard Henderson	rth@redhat.com
 i386 port		Jan Hubicka		jh@suse.cz
 i386 port		Uros Bizjak		ubizjak@gmail.com
-ia64 port		Jim Wilson		wilson@tuliptree.org
+ia64 port		Jim Wilson		wilson@codesourcery.com
 ia64 port		Steve Ellcey		sje@cup.hp.com
 iq2000 port		Nick Clifton		nickc@redhat.com
 m32c port		DJ Delorie		dj@redhat.com
@@ -155,7 +155,7 @@ libobjc			Nicola Pero		nicola.pero@meta-
 libobjc			Andrew Pinski		pinskia@gmail.com
 loop discovery		Michael Hayes		m.hayes@elec.canterbury.ac.nz
 soft-fp			Joseph Myers		jsm@polyomino.org.uk
-scheduler (+ haifa)	Jim Wilson		wilson@tuliptree.org
+scheduler (+ haifa)	Jim Wilson		wilson@codesourcery.com
 scheduler (+ haifa)	Michael Meissner	gnu@the-meissners.org
 scheduler (+ haifa)	Jeff Law		law@redhat.com
 scheduler (+ haifa)	Vladimir Makarov	vmakarov@redhat.com
@@ -163,7 +163,7 @@ modulo-scheduler	Ayal Zaks		zaks@il.ibm.
 reorg			Jeff Law		law@redhat.com
 caller-save.c		Jeff Law		law@redhat.com
 callgraph		Jan Hubicka		jh@suse.cz
-debugging code		Jim Wilson		wilson@tuliptree.org
+debugging code		Jim Wilson		wilson@codesourcery.com
 dwarf debugging code	Jason Merrill		jason@redhat.com
 c++ runtime libs	Paolo Carlini		paolo.carlini@oracle.com
 c++ runtime libs	Gabriel Dos Reis	gdr@integrable-solutions.net

             reply	other threads:[~2009-04-27 19:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 20:11 Jim Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-31 11:14 Update " Ramana Radhakrishnan
2005-12-07  3:48 Adam Nemet
2002-07-15 14:25 Neil Booth

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=1240862062.3278.70.camel@localhost.localdomain \
    --to=wilson@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.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).