public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Glenn Strauss <gs-cygwin.com@gluelogic.com>
Cc: cygwin@cygwin.com
Subject: Re: How to test Cygwin 3.5 using github actions
Date: Thu, 18 Jan 2024 15:10:11 +0000	[thread overview]
Message-ID: <d4a2e7bc-ff68-4c39-82a3-6e441517c411@dronecode.org.uk> (raw)
In-Reply-To: <ZagN9piLM-QSBKj8@xps13>

On 17/01/2024 17:27, Glenn Strauss via Cygwin wrote:
> On Wed, Jan 17, 2024 at 12:44:32PM +0100, Corinna Vinschen via Cygwin wrote:
>> Hi folks,
>>
>> we're planning to release Cygwin 3.5 end of this month (Jan 2024) if
>> nothing serious crops up.
> 
> Was: Re: [ANNOUNCEMENT] Cygwin 3.5 is coming soon, please test!
> 
> Corinna: Cygwin 3.5 works fine when tested with the lighttpd test suite.
> 
> 
> For others who might try something similar on their own repos:
> 
[...]
> 
> Hey Jon, would you accept a pull request to add an option to add -t to
> the call to setup.exe in cygwin-install-action?

Sure, that seems like a useful feature to add.


  parent reply	other threads:[~2024-01-18 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 11:44 [ANNOUNCEMENT] Cygwin 3.5 is coming soon, please test! Corinna Vinschen
2024-01-17 17:27 ` How to test Cygwin 3.5 using github actions Glenn Strauss
2024-01-18  9:55   ` Corinna Vinschen
2024-01-18 15:10   ` Jon Turney [this message]
2024-01-18  8:28 ` [ANNOUNCEMENT] Cygwin 3.5 is coming soon, please test! Brian Inglis
2024-01-21 11:18 ` Exponential slowdown for deep paths in Cygwin 3.5 Dan Shelton
2024-02-09  0:41   ` Dan Shelton

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=d4a2e7bc-ff68-4c39-82a3-6e441517c411@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=gs-cygwin.com@gluelogic.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).