From: Jon Turney <jon.turney@dronecode.org.uk>
To: Thomas Wolff <towo@towo.net>, cygwin-developers@cygwin.com
Subject: Re: cygwin build
Date: Thu, 3 Aug 2023 14:13:10 +0100 [thread overview]
Message-ID: <717c5b21-f532-9716-4f2d-7f0c0e2ac92f@dronecode.org.uk> (raw)
In-Reply-To: <9f4eb8f4-4020-a26d-6deb-50da884ad6af@towo.net>
On 02/08/2023 07:36, Thomas Wolff wrote:
> Am 01.08.2023 um 23:27 schrieb Corinna Vinschen:
>> On Aug 1 23:05, Thomas Wolff wrote:
>>> I took some of the latest cygwin snapshots (by the way, there are no
>>> newer
>>> ones on the snapshots page):
>> Snapshots are no longer produced. You should download the latest
>> test versions via setup.
> So what if I need an older version?
I'd suggest maybe start by bisecting old released versions, which are
available via the Cygwin Time Machine.
(We never promised to keep an infinitely deep history of snapshots, but
CTM does archive test versions, so going forward we'll have those
available from it, also)
next prev parent reply other threads:[~2023-08-03 13:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6f0bfdf8-a557-0540-0367-6846406f941d@towo.net>
2023-08-01 21:05 ` Rare character glitch in pty? Thomas Wolff
2023-08-01 21:27 ` Corinna Vinschen
2023-08-02 6:36 ` cygwin build Thomas Wolff
2023-08-02 6:42 ` Takashi Yano
2023-08-02 8:09 ` Corinna Vinschen
2023-08-03 8:21 ` Thomas Wolff
2023-08-03 13:12 ` Jon Turney
2023-08-05 18:18 ` Thomas Wolff
2023-08-05 22:20 ` Takashi Yano
2023-08-06 6:51 ` Thomas Wolff
2023-08-06 18:53 ` Jon Turney
2023-08-07 6:11 ` Thomas Wolff
2023-08-07 8:25 ` Corinna Vinschen
2023-08-03 13:13 ` Jon Turney [this message]
2023-08-01 22:35 ` Rare character glitch in pty? Takashi Yano
2023-08-02 6:32 ` Thomas Wolff
2023-08-02 8:00 ` Takashi Yano
2023-08-02 13:16 ` Takashi Yano
2023-08-04 8:52 ` Takashi Yano
2023-08-04 11:33 ` Takashi Yano
2023-08-05 7:53 ` Thomas Wolff
2023-08-05 8:10 ` Takashi Yano
2023-08-07 8:28 ` Corinna Vinschen
2023-08-07 11:38 ` Takashi Yano
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=717c5b21-f532-9716-4f2d-7f0c0e2ac92f@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-developers@cygwin.com \
--cc=towo@towo.net \
/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).