public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Modica <modica@sgi.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
	linux-scsi@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-hams@vger.kernel.org, linux-ppp@vger.kernel.org
Subject: Re: ECN is on!
Date: Tue, 22 May 2001 09:18:11 -0500	[thread overview]
Message-ID: <3B0A7523.8641A688@sgi.com> (raw)
In-Reply-To: <20010522131031.C5947@mea-ext.zmailer.org> <15114.18990.597124.656559@pizda.ninka.net>

"David S. Miller" wrote:
> 
> Matti Aarnio writes:
>  > I am contemplating to periodically turn off the ECN bit to
>  > let email out, but DaveM has veto there.
> 
> I veto, the whole point of moving to ECN was to make a statement and
> get people to fix their kit.
> 
> We will remove these people, that's all.
> 
> Later,
> David S. Miller
> davem@redhat.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org

Perhaps it's none of my business, but it doesn't seem very sporting to
just turn something on that breaks stuff and say "you had fair
warning".  Why not shut it back off, issue a statement saying it works
now and will be re-enabled on June 10th or something, and everyone must
do thus and so or they will break on that day?

Vague things like "it'll be turned on real soon now" or ASAP really mean
"never" since admins always have things with real deadlines at the top
of their list.

Steve
-- 
Steve Modica
Manager - Networking Drivers Group
"Give a man a fish, and he will eat for a day, hit him with a fish and
he leaves you alone" - me

  parent reply	other threads:[~2001-05-22 14:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22 10:10 ECN is on! Matti Aarnio
2001-05-22 11:14 ` David S. Miller
2001-05-22 11:18   ` Alan Cox
2001-05-22 12:51     ` Richard Gooch
2001-05-22 11:51   ` Brent D. Norris
2001-05-22 12:39     ` Erik Mouw
2001-05-22 13:06     ` Richard Gooch
2001-05-22 15:59       ` Matti Aarnio
2001-05-22 16:20         ` Richard Gooch
2001-05-22 16:00       ` Tony Hoyle
2001-05-22 16:04         ` Matti Aarnio
2001-05-22 16:23         ` Richard Gooch
2001-05-22 17:03           ` Matti Aarnio
2001-05-22 16:12       ` Rogier Wolff
2001-05-22 16:27         ` Steve Modica
2001-05-23  9:58           ` Matti Aarnio
2001-05-22 21:46       ` Matthias Andree
2001-05-22 14:18   ` Steve Modica [this message]
2001-05-22 14:57   ` Final Warning [ was: ECN is on! ] David Relson
2001-05-22 15:07     ` Matti Aarnio
2001-05-22 16:55     ` Joe Barr
2001-05-22 17:11       ` Matti Aarnio
2001-05-22 11:36 ` ECN is on! Bohdan Vlasyuk
2001-05-22 12:07 ` Graham Murray
  -- strict thread matches above, loose matches on Subject: below --
2001-05-22 16:39 Christian, Chip

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=3B0A7523.8641A688@sgi.com \
    --to=modica@sgi.com \
    --cc=davem@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=linux-ppp@vger.kernel.org \
    --cc=linux-scsi@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