From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Snapshot of Cygwin from Windows XP era
Date: Fri, 29 Oct 2021 11:29:32 +0100 [thread overview]
Message-ID: <DB3PR0202MB356162E45A29F19B166C2337E7879@DB3PR0202MB3561.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <20211028233728.GY32501@ming.fruitbat.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 2014 bytes --]
On 29/10/2021 00:37, Peter A. Castro wrote:
> On Thu, Oct 28, 2021 at 07:24:59PM +0100, Hamish McIntyre-Bhatty wrote:
>> On 28/10/2021 17:14, Peter A. Castro wrote:
>>> On Thu, Oct 28, 2021 at 11:14:59AM +0100, Hamish McIntyre-Bhatty wrote:
>>>
>>> Greetings, Hamish,
>>>
>>>> On 25/10/2021 17:37, Peter A. Castro wrote:
>>>>> On Sat, Oct 23, 2021 at 05:14:12PM +0100, Cygwin List wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> I was wondering if there exists a snapshot of the Cygwin repos at a time
>>>>>> when Windows XP was still supported?
>>>>> Try the Cygwin Time Machine which has a continual collection of all
>>>>> Cygwin packages:
>>>>>
>>>>> http://www.crouchingtigerhiddenfruitbat.org/Cygwin/timemachine.html
>>>>>
>>>>> There you can find info specifically about the last XP release.
>>>>>
>>>>> Hope that helps, and good luck!
>>>>>
>>>>>> Thanks,
>>>>>> Hamish
>>>> Cheers, found this later, but good to have a mention in the archive :)
>>>>
>>>> Could we link to the time machine from cygwin.org? It's not very easy to
>>>> find as it is.
>>> Really? Google "Cygwin Time Machine" and it's the very first link. :)
>>>
>>> But, if you want to suggest something on the Cygwin list, be my guest.
>> Well yes, but if you don't know that's what it's called...
> Ah... That is a valid point if one dives into Cygwin for the first time...
>
> Perhaps I could have choosen a more descriptive name? Maybe "Cygwin
> Archive"? But "Cygwin Archive" is a bit to broad and one could argue
> that the cygwin.com site is the (rightfully) current "archive" of
> Cygwin. Wouldn't want to detract from that.
>
> Well, people also search, more commonly, for "The last version of
> Cygwin to support XP" and that takes you to a Stackoverflow article
> which also talks about the Cygwin Time Machine.
>
> So, eventually, all roads lead to Rome...err, I mean the "Time Machine" :)
Fair point(s). I guess I'm bad at searching for things, wouldn't be the
first time :)
Hamish
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3175 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-10-29 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 16:14 Hamish McIntyre-Bhatty
2021-10-23 16:40 ` Ilya Basin
2021-10-23 18:13 ` Hamish McIntyre-Bhatty
2021-10-25 16:37 ` Peter A. Castro
[not found] ` <DB3PR0202MB3561ECC8E24BC980B4FEE1FCE7869@DB3PR0202MB3561.eurprd02.prod.outlook.com>
[not found] ` <20211028161426.GX32501@ming.fruitbat.org>
[not found] ` <DB3PR0202MB3561FDC7BAF5D2FE6A339BEEE7869@DB3PR0202MB3561.eurprd02.prod.outlook.com>
[not found] ` <20211028233728.GY32501@ming.fruitbat.org>
2021-10-29 10:29 ` Hamish McIntyre-Bhatty [this message]
2021-11-16 9:28 ` Hamish McIntyre-Bhatty
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=DB3PR0202MB356162E45A29F19B166C2337E7879@DB3PR0202MB3561.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.uk \
--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).