From owner-freebsd-hackers Thu Aug 20 12:35:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07497 for freebsd-hackers-outgoing; Thu, 20 Aug 1998 12:35:40 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA07488 for ; Thu, 20 Aug 1998 12:35:36 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0z9a86-0002mx-00; Thu, 20 Aug 1998 13:12:14 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id NAA21912; Thu, 20 Aug 1998 13:12:36 -0600 (MDT) Message-Id: <199808201912.NAA21912@harmony.village.org> To: Brian Beattie Subject: Re: proposal to not change time_t Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 20 Aug 1998 08:56:01 PDT." References: Date: Thu, 20 Aug 1998 13:12:36 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Personally, I'd like to see a 64-bit time_t that is the number of 100nS units since 1600, like another well known OS uses. Too bad time_t is documented to be seconds... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message