From owner-freebsd-arch  Sat Jun  2 12:56:15 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4992437B422; Sat,  2 Jun 2001 12:56:13 -0700 (PDT)
	(envelope-from drosih@rpi.edu)
Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47])
	by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f52JuCS15604;
	Sat, 2 Jun 2001 15:56:12 -0400
Mime-Version: 1.0
X-Sender: drosih@mail.rpi.edu
Message-Id: <p05100e11b73ef4f9f5d1@[128.113.24.47]>
In-Reply-To: <20010602124907.G31257@dragon.nuxi.com>
References: <200106012318.f51NI8w38590@bunrab.catwhisker.org>
 <200106020823.f528N5O98998@earth.backplane.com>
 <20010602085237.A73968@dragon.nuxi.com>
 <200106021739.f52Hd9V03943@earth.backplane.com>
 <p05100e0fb73ee9d458f7@[128.113.24.47]>
 <20010602124907.G31257@dragon.nuxi.com>
Date: Sat, 2 Jun 2001 15:56:10 -0400
To: obrien@FreeBSD.ORG
From: Garance A Drosihn <drosih@rpi.edu>
Subject: Re: time_t definition is wrong
Cc: Matt Dillon <dillon@earth.backplane.com>,
	David Wolfskill <david@catwhisker.org>, arch@FreeBSD.ORG,
	freebsd-standards@bostonradio.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-arch.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-arch>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-arch>
X-Loop: FreeBSD.ORG

At 12:49 PM -0700 6/2/01, David O'Brien wrote:
>On Sat, Jun 02, 2001, Garance A Drosihn wrote:
>  > I don't have any strong feeling about what is "right" in this
>  > case, but I do think it would be appropriate to back out the
>>  change to time_t until the question *is* correctly sorted out.
>
>I don't see why?  We can't even agree there is a problem.  And if
>dangerous kernel commits can stay in, so can this one.

...also, in situations where "we can't agree there is a problem",
I thought we were supposed to favor the status quo (ie, pre-update)
over rushing in to fix something which we can not agree is broken.

-- 
Garance Alistair Drosehn            =   gad@eclipse.acs.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message