From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: Ben Greear <greearb@candelatech.com>,
akpm@osdl.org, netdev@oss.sgi.com, mbm@alt.org
Subject: Re: Fw: [Bugme-new] [Bug 3657] New: downed interfaces acting as aliases
Date: Fri, 29 Oct 2004 09:39:27 +0200 [thread overview]
Message-ID: <20041029073927.GB15301@wotan.suse.de> (raw)
In-Reply-To: <20041029000651.6fd7360f.davem@davemloft.net>
> People hate it that when there's a decision of whether to
> reply to something or not, we do whatever we can to reply
> to packets we receive if we can find a way to do so. This
> approache increases the likelyhood that two hosts can
> communicate successfully.
I bet it's actually only a very small minority that is complaining
about this. The silent majority just sees a working network.
-Andi
prev parent reply other threads:[~2004-10-29 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 6:46 Fw: [Bugme-new] [Bug 3657] New: downed interfaces acting as aliases Andrew Morton
2004-10-29 6:45 ` David S. Miller
2004-10-29 7:10 ` Ben Greear
2004-10-29 7:06 ` David S. Miller
2004-10-29 7:28 ` Ben Greear
2004-10-29 7:39 ` Andi Kleen [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=20041029073927.GB15301@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=greearb@candelatech.com \
--cc=mbm@alt.org \
--cc=netdev@oss.sgi.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).