From: Ralf Baechle <ralf@linux-mips.org>
To: John Crispin <john@phrozen.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 1/2] MAINTAINERS: change my email address
Date: Mon, 9 May 2016 17:20:30 +0200 [thread overview]
Message-ID: <20160509152030.GC28818@linux-mips.org> (raw)
In-Reply-To: <1462435076-48703-1-git-send-email-john@phrozen.org>
On Thu, May 05, 2016 at 09:57:55AM +0200, John Crispin wrote:
> The old address is no longer valid. Use the my new one instead.
Both applied. I take it you're going to send patches to change the remaining
files to other maintainers? It'd probably be easier if you'd ask Linus
to run something like sed -e 's/blogic@openwrt.org/blogic@phrozen.org/'
over the tree.
Ralf
prev parent reply other threads:[~2016-05-09 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 7:57 [PATCH 1/2] MAINTAINERS: change my email address John Crispin
2016-05-05 7:57 ` [PATCH 2/2] arch: mips: " John Crispin
2016-05-09 15:20 ` Ralf Baechle [this message]
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=20160509152030.GC28818@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=john@phrozen.org \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.