From: "Martinez, Joshua" <joshua.martinez1@hp.com>
To: Jon Turney <jon.turney@dronecode.org.uk>,
"cygwin-announce@cygwin.com" <cygwin-announce@cygwin.com>
Subject: RE: cygport 0.36.2-1
Date: Thu, 13 Apr 2023 16:26:44 +0000 [thread overview]
Message-ID: <MW5PR84MB20823102C654ADD3A0AE2EB7AA989@MW5PR84MB2082.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <726c5376-abc8-bceb-a3f9-419a39c78684@dronecode.org.uk>
Can I get removed from this list?
Regards,
Joshua
-----Original Message-----
From: Cygwin-announce <cygwin-announce-bounces+joshua.martinez1=hp.com@cygwin.com> On Behalf Of Jon Turney
Sent: Thursday, April 13, 2023 9:26 AM
To: cygwin-announce@cygwin.com
Subject: cygport 0.36.2-1
CAUTION: External Email
The following packages have been uploaded to the Cygwin distribution:
* cygport-0.36.1-1
cygport is the standard method for building and maintaining packages for the Cygwin distribution.
Highlights of this release:
Stripping of executables is now parallelized. With many cores, this can result in a large speed up for packages with many executable files.
(Thanks to Achim Gratz)
Achim Gratz (1):
lib/src_postinst.cygpart: parallelize __prepstrip
Brian Inglis (1):
lib/src_fetch.cygpart: iterate thru mirror lists if downloads fail
Jon Turney (4):
Try to turn case-sensitivity on for the working directory on Cygwin
autotools: Update documented range of WANT_AUTOMAKE values
Move creation of dbgsrc.out.0 before checking if RESTRICT contains 'strip'
Bump version to 0.36.2
Ken Brown (1):
git: Try 'main' if there's no master branch
Marco Atzeri (1):
python-wheel: Allow projects without setup.py or setup.cfg, only pyproject.toml (PEP 518)
prev parent reply other threads:[~2023-04-13 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <30f1d642-a044-a898-a9d7-ff6744f2f2a5@dronecode.org.uk>
2023-04-13 16:25 ` Jon Turney
2023-04-13 16:26 ` Martinez, Joshua [this message]
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=MW5PR84MB20823102C654ADD3A0AE2EB7AA989@MW5PR84MB2082.NAMPRD84.PROD.OUTLOOK.COM \
--to=joshua.martinez1@hp.com \
--cc=cygwin-announce@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).