From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Pekka Savola <pekkas@netcore.fi>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH] Rationalise email address: Network Specific Parts
Date: Mon, 13 Oct 2008 14:12:09 +0100 [thread overview]
Message-ID: <20081013141209.7cea1ccd@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.00.0810131351270.28474@netcore.fi>
> cases would be just using a name without any email address. It's not
> like there are multiple alan coxes actively contributing to the
> kernel.
Well ukuu.org.uk is my own domain so hopefully that'll be a good reliable
long term address.
And there are multiple Alan Cox's working on Linux related projects even
if not currently the kernel. I've met two...
next prev parent reply other threads:[~2008-10-13 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 9:54 [PATCH] Rationalise email address: Network Specific Parts Alan Cox
2008-10-13 10:06 ` David Miller
2008-10-13 10:53 ` Pekka Savola
2008-10-13 13:12 ` Alan Cox [this message]
2008-10-13 14:24 ` Xavier Bestel
2008-10-13 14:36 ` Américo Wang
2008-10-13 14:48 ` Linus Torvalds
2008-10-14 2:01 ` David Miller
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=20081013141209.7cea1ccd@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=torvalds@linux-foundation.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