From: Patrick McHardy <kaber@trash.net>
To: "Fred L. Templin" <osprey67@yahoo.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 01/01] iproute2-2.6.23: RFC4214 Support (3)
Date: Sun, 11 Nov 2007 04:26:44 +0100 [thread overview]
Message-ID: <47367674.2040208@trash.net> (raw)
In-Reply-To: <753838.51488.qm@web82105.mail.mud.yahoo.com>
Fred L. Templin wrote:
> What do you suggest?
To remove them unless there's some justification
to keep them.
next parent reply other threads:[~2007-11-11 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <753838.51488.qm@web82105.mail.mud.yahoo.com>
2007-11-11 3:26 ` Patrick McHardy [this message]
2007-11-08 20:29 [PATCH 01/05] ipv6: RFC4214 Support (2) osprey67
2007-11-10 0:35 ` [PATCH 05/05] ipv6: RFC4214 Support (3) osprey67
2007-11-10 0:42 ` [PATCH 01/01] iproute2-2.6.23: " osprey67
2007-11-10 1:04 ` Patrick McHardy
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=47367674.2040208@trash.net \
--to=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=osprey67@yahoo.com \
/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).