From: David Miller <davem@davemloft.net>
To: alan@lxorguk.ukuu.org.uk
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 03:06:46 -0700 (PDT) [thread overview]
Message-ID: <20081013.030646.123824121.davem@davemloft.net> (raw)
In-Reply-To: <20081013105453.35eece02@lxorguk.ukuu.org.uk>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: Mon, 13 Oct 2008 10:54:53 +0100
> Clean up the various different email addresses of mine listed in the code
> to a single current and valid address. As Dave says his network merges
> for 2.6.28 are now done this seems a good point to send them in where
> they won't risk disrupting real changes.
>
> Signed-off-by: Alan Cox <alan@redhat.com>
I'm happy to suck this in via my net-2.6 tree.
next prev parent reply other threads:[~2008-10-13 10:07 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 [this message]
2008-10-13 10:53 ` Pekka Savola
2008-10-13 13:12 ` Alan Cox
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=20081013.030646.123824121.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).