Re: Millennium

Article View: alt.games.descent

Article #93489

#93489

From: Blair Nowakowsky
Date: Mon, 16 Jun 1997 00:00

34 lines
1711 bytes

In article <01bc766b$59eb43a0$651c...@venger-no-fear.intervoice.com>, "Michael E. Chester II" <mche...@utdallas.edu> wrote:
>
>
>phelper <phe...@onramp.net.gov> wrote in article
><339e0344...@news.onramp.net>...
>> 
>> >
>> >I think each century starts with 0, 1000, 2000 and so on...
>> >
>> >/Michael
>> 
>> C'mon bro...  you don't count to 10 starting with zero, do you?
>
>To whomever it may concern on this topic, the anniversary of the millenium
>begins in 2001.
>
>The first year was 1. At year 1000, we had completed only 999 years. At
>1001, we had completed 1000. So, the new millenium will always begin at a
>year xxx1.
>
>\  /
> \/enger

I heard one theory that the first century only had 99 years, not 100.  This 
then make all of the subsequent centuries start at the 00 date.  I like that 
better.  

 This all started with that Gregorian monk.  He forgot about 0. :-(

Blair.

Its all about how you count,  One, Two, Four, Five, Six, Seven, Eight, Ten !!!

Technical Details

Message-ID: <5o3tv5$802@mercury.arc.ab.ca>

Path: mbox-mo1.pugleaf.net!unknown!not-for-mail

References:

<01bc750e$7441ea00$5af62581@dferner> <5njrcp$ndc@limes.air.saab.se> <339e0344.1446549@news.onramp.net> <01bc766b$59eb43a0$651c10ac@venger-no-fear.intervoice.com>

Show Full Headers

Complete Article Headers

From: nowakowsky@arc.ab.ca.stopspam (Blair Nowakowsky)
Subject: Re: Millennium
Date: 1997/06/16
Message-ID: <5o3tv5$802@mercury.arc.ab.ca>
X-Deja-AN: 249072379
References: <01bc750e$7441ea00$5af62581@dferner> <5njrcp$ndc@limes.air.saab.se> <339e0344.1446549@news.onramp.net> <01bc766b$59eb43a0$651c10ac@venger-no-fear.intervoice.com>
Organization: Alberta Research Council
Newsgroups: comp.sys.ibm.pc.hardware.chips,comp.sys.ibm.pc.hardware.video,alt.games.quake,alt.games.duke3d,alt.games.mechwarrior2,alt.games.descent,comp.sys.ibm.pc.games.strategic,recipes.babies,alt.games.redalert,chile.futbol
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Reply to Parent Message