mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.4.15-pre9
Date: Mon, 26 Nov 2001 10:18:45 -0500	[thread overview]
Message-ID: <200111261518.fAQFIj201541@deathstar.prodigy.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111221046170.1479-100000@penguin.transmeta.com>
In-Reply-To: <20011122134700.A4966@bee.lk>

In article <Pine.LNX.4.33.0111221046170.1479-100000@penguin.transmeta.com> 
  torvalds@transmeta.com claimed this objective:
>
>On Thu, 22 Nov 2001, Anuradha Ratnaweera wrote:
>>
>> On Wed, Nov 21, 2001 at 10:44:30PM -0800, Linus Torvalds wrote:
>> >
>> > I think I'm ready to hand this over to Marcelo.
>>
>> Aren't you going to include Tim Schmielau's patch to handle uptime larger than
>> 497 days?  It is a cool feature we always liked to have.
>
>Quite frankly, right now I'm in "handle only bugs that can crash the
>system mode". Anything that takes 497 days to see is fairly low on my
>priority list. My highest priority, in fact, is to get 2.4.15 out without
>any embarrassment.

Back in the 60's when GE was still a mainframe manufacturer they had a
counter which rolled over at about 35 days. When it started failing
their competitors had good time with "GECOS fails to fail as expected."
That *is* an embarrassment.

con06:news> uptime
  9:56am  up 427 days, 19:00,  2 users,  load average: 0.87, 0.88, 0.83

-- 
bill davidsen <davidsen@tmr.com>
  His first management concern is not solving the problem, but covering
his ass. If he lived in the middle ages he'd wear his codpiece backward.

  parent reply	other threads:[~2001-11-26 15:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22  6:44 Linux-2.4.15-pre9 Linus Torvalds
2001-11-22  7:47 ` Linux-2.4.15-pre9 Anuradha Ratnaweera
2001-11-22 18:52   ` Linux-2.4.15-pre9 Linus Torvalds
2001-11-22 19:34     ` Linux-2.4.15-pre9 Alexander Viro
2001-11-22 19:46       ` Linux-2.4.15-pre9 Tom Rini
2001-11-23 16:20     ` Linux-2.4.15-pre9 Michael H. Warfield
2001-11-26 11:52     ` PATCH 2.5.0 kill read_ahead array Martin Dalecki
2001-11-26 16:34       ` Andreas Dilger
2001-11-26 16:53         ` Martin Dalecki
2001-11-22 19:16   ` Linux-2.4.15-pre9 Tim Schmielau
2001-11-26 15:18   ` bill davidsen [this message]
2001-11-22  8:41 ` [PATCH] fix SCSI non-blocksize reads Erik Andersen
2001-11-22 17:09   ` Linus Torvalds
2001-11-22 17:20     ` Erik Andersen
2001-11-22 18:40       ` Linus Torvalds
2001-11-24  0:04         ` Erik Andersen
2001-11-22 22:10 Linux-2.4.15-pre9 Leif Sawyer
2001-11-22 22:21 ` Linux-2.4.15-pre9 Linus Torvalds
2001-11-23 16:20   ` Linux-2.4.15-pre9 Jeff Garzik
2001-11-22 22:27 ` Linux-2.4.15-pre9 Linus Torvalds

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=200111261518.fAQFIj201541@deathstar.prodigy.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®