From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/4] net: ipmr netlink interface for route dumping
Date: Tue, 27 Apr 2010 20:41:04 +0200 [thread overview]
Message-ID: <4BD72FC0.8080109@trash.net> (raw)
In-Reply-To: <20100427.100345.241441437.davem@davemloft.net>
David Miller wrote:
> Whoa, there are three of you now?!?!?!
>
> :-)
>
That would be nice, I'd have my two clones do all the work :)
Not sure what happened, some mishandling of git send-email
apparently :)
next prev parent reply other threads:[~2010-04-27 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 13:26 [PATCH 0/4] net: ipmr netlink interface for route dumping Patrick, McHardy, kaber
2010-04-27 13:26 ` [PATCH 1/3] net: fib_rules: mark arguments to fib_rules_register const and __net_initdata Patrick, McHardy, kaber
2010-04-27 13:26 ` [PATCH 2/3] net: rtnetlink: decouple rtnetlink address families from real address families Patrick, McHardy, kaber
2010-04-27 13:26 ` [PATCH 3/3] net: ipmr: add support for dumping routing tables over netlink Patrick, McHardy, kaber
2010-04-27 17:03 ` [PATCH 0/4] net: ipmr netlink interface for route dumping David Miller
2010-04-27 18:41 ` Patrick McHardy [this message]
2010-04-27 19:59 ` 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=4BD72FC0.8080109@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).