From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA} gd 2.2.5-2
Date: Sun, 11 Nov 2018 22:38:00 -0000 [thread overview]
Message-ID: <6d0f3b22-6f10-582c-a3c2-c74ff3ff074b@gmail.com> (raw)
In-Reply-To: <667fcf36-4d7c-88ca-9f67-1fe03639eb80@cornell.edu>
Am 11.11.2018 um 22:25 schrieb Ken Brown:
> Although there's been no new upstream release since the last Cygwin release,
> there have been some bug fixes (including one that I just found to fix a crash
> on 32-bit Cygwin), which warrant a new release.
>
> I'm attaching my cygport file and the one patch that can't be gotten by "cygport
> fetch". I'm also attaching, for comparison, the cygport file from the current
> Cygwin release.
>
> There are two test failures on 32-bit Cygwin. (There were four before I fixed
> the crash I mentioned above.) I've reported them upstream and hope to get them
> fixed eventually.
>
> Ken
>
it looks good to me.
I updated the cygwin-pkg-maint
Regards
Marco
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
next prev parent reply other threads:[~2018-11-11 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 21:25 Ken Brown
2018-11-11 22:38 ` Marco Atzeri [this message]
2018-11-12 14:22 ` Andrew Schulman
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=6d0f3b22-6f10-582c-a3c2-c74ff3ff074b@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@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).