From: Michael Haubenwallner <michael.haubenwallner@ssi-schaefer.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.1.0-0.6 (TEST)
Date: Tue, 24 Sep 2019 07:38:00 -0000 [thread overview]
Message-ID: <e55a275c-5b77-c03f-ab99-0dc207825b3b@ssi-schaefer.com> (raw)
In-Reply-To: <announce.20190922101035.2703-1-kbrown@cornell.edu>
Hi,
On 9/22/19 4:11 PM, Ken Brown wrote:
> The following packages have been uploaded to the Cygwin distribution
> as test releases:
so I do have some Azure Pipelines running, which perform an automated
Cygwin setup from scratch before building my pet project there.
But then, I also do want to autotest cygwin1.dll itself a little, so I want
to use cygwin TEST versions or similar. Because setup.exe does not
support that right now from the commandline, I do use snapshot builds of
cygwin1.dll, because identifying the last snapshot felt easier than
identifying the last test release.
However, I do see the last snapshot dating back to 2019-08-19, which is
rather old compared to test releases seen since then.
Is there something broken with building snapshots, or is it just not automated?
Thanks!
/haubi/
--
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:[~2019-09-24 7:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 16:24 Ken Brown
2019-09-24 7:38 ` Michael Haubenwallner [this message]
2019-09-24 12:50 ` Ken Brown
2019-09-24 23:05 ` Ken Brown
2019-09-25 18:30 ` Takashi Yano
2019-09-26 12:51 ` Takashi Yano
2019-09-26 14:38 ` Ken Brown
2019-10-02 14:04 ` Michael Haubenwallner
2019-10-02 18:24 ` Ken Brown
2019-10-03 10:44 ` Takashi Yano
2019-10-10 10:44 ` Michael Haubenwallner
2019-10-11 9:25 ` Takashi Yano
2019-10-14 11:07 ` Michael Haubenwallner
2019-10-16 12:32 ` Takashi Yano
2019-10-18 11:36 ` Takashi Yano
2019-10-16 14:34 ` Takashi Yano
2019-10-16 16:34 ` Michael Haubenwallner
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=e55a275c-5b77-c03f-ab99-0dc207825b3b@ssi-schaefer.com \
--to=michael.haubenwallner@ssi-schaefer.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).