From: Marco Atzeri <marco.atzeri@gmail.com>
To: Tony Kelman <tony@kelman.net>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Test: cmake-3.13.1-1
Date: Wed, 05 Jun 2019 09:07:00 -0000 [thread overview]
Message-ID: <f8e15a69-04ba-f37e-95b5-4dd55ebe2b3f@gmail.com> (raw)
In-Reply-To: <CY4PR22MB07731E5A2654E198D7711CC3A7150@CY4PR22MB0773.namprd22.prod.outlook.com>
Am 05.06.2019 um 01:22 schrieb Tony Kelman:
> See below what I said in both January and November the last times we had any conversation on this. cmake_minimum_required, project_injected, and CommandLine test failures are new and I'd personally come to a definitive thoroughly researched conclusion on what's causing them before making a release. But I don't intend on making any releases of cygwin packages any time soon, so you can do whatever you want here.
>
>
I will release cmake-3.14.5 as soon I finish the packages
waiting for the perfect package is not a good idea IMHO,
when you have time you can look for the a solution of
test failures.
Regards
Marco
---
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:[~2019-06-05 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 9:27 Marco Atzeri
2019-05-28 2:39 ` Steven Penny
2019-05-30 8:11 ` Marco Atzeri
2019-05-30 16:05 ` Yaakov Selkowitz
2019-06-04 7:42 ` Marco Atzeri
2019-06-04 23:22 ` Tony Kelman
2019-06-05 9:07 ` Marco Atzeri [this message]
2019-05-30 10:31 Ivan Shynkarenka
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=f8e15a69-04ba-f37e-95b5-4dd55ebe2b3f@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=tony@kelman.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).