From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: glib2.0 2.64.6-1 (TEST)
Date: Sun, 20 Aug 2023 14:00:33 +0100 [thread overview]
Message-ID: <afaa89b3-523e-f26f-23ff-15d52494d306@dronecode.org.uk> (raw)
In-Reply-To: <adaf0c49-3ab2-c883-474e-f9e00f79c5bb@dronecode.org.uk>
On 02/07/2023 15:30, Jon Turney wrote:
>
> The following packages have been uploaded to the Cygwin distribution:
>
> * libglib2.0_0-2.64.6-1
> * libglib2.0-devel-2.64.6-1
> * libglib2.0-doc-2.64.6-1
>
> GLib is the low-level core library that forms the basis for projects
> such as GTK+ and GNOME. It provides data structure handling for C,
> portability wrappers, and interfaces for such runtime functionality as
> an event loop, threads, dynamic loading, and an object system.
>
> This is a long-needed update to a later upstream release. Thanks to Ken
> Brown for doing lots of the actual hard work involved.
>
> There are many test-suite failures, however, as far as I can tell, they
> are not regressions, so this should work as well as it ever did.
>
These packages have been promoted from test to current.
parent reply other threads:[~2023-08-20 13:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <adaf0c49-3ab2-c883-474e-f9e00f79c5bb@dronecode.org.uk>]
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=afaa89b3-523e-f26f-23ff-15d52494d306@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).