From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.11.2-0.1
Date: Wed, 31 Oct 2018 15:16:00 -0000 [thread overview]
Message-ID: <7ecbe626-6e4e-6932-9dcf-23cbe51e15cb@gmail.com> (raw)
In-Reply-To: <afdd9a00791e604db819aaad5c101053@internetgruppen.dk>
Am 31.10.2018 um 14:54 schrieb Niels Kristian "Ænkå" Jensen:
> This thread asks for testers. I've read the
>
> https://cygwin.com/faq.html and in particular:
> https://cygwin.com/faq.html#faq.setup.snapshots
>
> without finding a way to run the test release other than simply
> replacing the cygwin1.dll with the snapshot one. It seems to run fine,
> I've deployed to one of the Jenkins build agents some hours ago.
>
> My question: Is a "test" version of the setup program with an updated
> setup.ini available somewhere?
It can be installed by the standard setup,
just select 2.11.2-0.1 from the available versions of
cygwin package.
The new setup show better the test versions available.
https://www.cygwin.com/ml/cygwin/2018-10/msg00167.html
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-10-31 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 13:54 Niels Kristian "Ænkå" Jensen
2018-10-31 15:16 ` Marco Atzeri [this message]
2018-11-01 8:20 ` Niels Kristian "Ænkå" Jensen
2018-11-01 10:13 ` Marco Atzeri
-- strict thread matches above, loose matches on Subject: below --
2018-10-30 9:24 Corinna Vinschen
2018-10-30 11:41 ` Marco Atzeri
2018-10-30 11:45 ` Corinna Vinschen
2018-10-30 12:46 ` Marco Atzeri
2018-10-30 14:25 ` Achim Gratz
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=7ecbe626-6e4e-6932-9dcf-23cbe51e15cb@gmail.com \
--to=marco.atzeri@gmail.com \
--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).