From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Date of first Cygwin release / 25th Anniversary
Date: Thu, 24 Sep 2020 01:44:22 -0600 [thread overview]
Message-ID: <926cf86e-d8a9-444b-2a15-0fe1d1db29db@SystematicSw.ab.ca> (raw)
In-Reply-To: <MN2PR09MB47299D499AC7A98A29C803339B380@MN2PR09MB4729.namprd09.prod.outlook.com>
On 2020-09-23 13:16, Buchbinder, Barry (NIH/NIAID) [E] via Cygwin wrote:
> On Wednesday, September 23, 2020 2:33 PM, David Eisner wrote:
>> Cygwin started in 1995.[1] Does anybody know the date of the first release?
>> I recognize that there may be no definitive answer, depending on how one
>> defines "release."
>>
>> In any case, happy 25th anniversary, Cygwin! Thanks to everybody who made
>> it and continues to make it possible.
>>
>> [1] https://www.usenix.org/legacy/publications/library/proceedings/usenix-nt98/full_papers/noer/noer_html/noer.html
> Oct 18. See https://cygwin.com/pipermail/cygwin-talk/2005q4/001601.html
Schedule to watch the following on the 18th next month in celebration:
https://www.youtube.com/watch?v=FTlnV6_uaK4 🥳🎉🙌🎂🕯
[Custom, possibly Outlook-compatible, follow up email headers @ noon CA, US]
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-09-24 7:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 18:32 David Eisner
2020-09-23 19:16 ` Buchbinder, Barry (NIH/NIAID) [E]
2020-09-23 20:15 ` David Eisner
2020-09-23 23:18 ` Csaba Raduly
2020-09-24 7:44 ` Brian Inglis [this message]
2020-09-24 13:41 ` Morten Kjærulff
[not found] ` <1654722903.18588.1600889908653@mail.yahoo.com>
2020-09-23 19:53 ` Kevin Schnitzius
2020-10-13 18:50 ` Corinna Vinschen
2020-10-13 19:34 ` Allen Hewes
2020-10-18 18:45 ` David Eisner
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=926cf86e-d8a9-444b-2a15-0fe1d1db29db@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).