Mickey's calendar is not telling the truth.
There problem is there are a few things which happened in the days
beforehands (13th, 14th, 17th) as the decision to setup a repository
started being taken. It took a few days to get things imported just
right. Machines were slow back in those days, too.
There are teeny artifacts of those attempts, for instance in
ChangeLog.1 you can see the import attempts (I think on the 13th cvs
was crashing because of some large files in the repository).
The repository we use today is marked Oct 18, 1995 throughout, as
the 1.1 revision is many files. Many other things are that way too.
For a project so large, how else should we date it. First time I used
the name OpenBSD? Date the DNS record was allocated? Date web page went
up? Date other developers got accounts? Or should we set the date based
on some previous conversation with the NetBSD guys?
So, with that said,
CVSROOT: /cvs
Module name: src
Changes by: [EMAIL PROTECTED] 2005/10/14 09:06:10
Modified files:
usr.bin/calendar/calendars: calendar.openbsd
Log message:
assume niklas's dating for openbsd birth
CVSROOT: /cvs
Module name: src
Changes by: [EMAIL PROTECTED] 2005/10/14 09:09:25
Modified files:
usr.bin/calendar/calendars: calendar.openbsd
Log message:
doh! it was a wednesday. and fix the time as well then
And that is:
Oct 18 OpenBSD born, Wednesday 08:37:01 GMT, 1995
It's more important that we agree ;)
