From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.11.0-0.1
Date: Mon, 13 Aug 2018 08:36:00 -0000 [thread overview]
Message-ID: <57db6510-86bd-3cca-5cbe-b209949ff8ea@towo.net> (raw)
In-Reply-To: <announce.20180809202604.GN4180@calimero.vinschen.de>
Am 09.08.2018 um 22:26 schrieb Corinna Vinschen:
> Hi folks,
>
>
> I uploaded a new Cygwin test release 2.11.0-0.1
>
> I'm planning for a release end of August. Please test.
>
> =======================================================================
>
> What's new:
> -----------
>
> ...
>
> What changed:
> -------------
>
> ...
>
> Bug Fixes
> ---------
>
> ...
>
> - Fix Unicode table.
> Addresses: https://cygwin.com/ml/cygwin/2018-06/msg00248.html
So basically the update from Unicode 5.0 to Unicode 10.0 will be in the
release; maybe that's worth an explicit item in the "What changed" section?
Should we make that Unicode 11.0 still on this occasion, or did you
update already?
Thomas
--
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:[~2018-08-13 8:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 20:27 Corinna Vinschen
2018-08-10 0:05 ` Andrey Repin
2018-08-10 11:05 ` Houder
2018-08-10 11:43 ` Corinna Vinschen
2018-08-10 12:43 ` Houder
2018-08-13 7:47 ` Corinna Vinschen
2018-08-13 8:03 ` Houder
2018-08-13 8:23 ` Corinna Vinschen
2018-08-13 21:29 ` Houder
2018-08-13 22:16 ` Eric Blake
2018-08-13 22:26 ` Houder
2018-08-14 6:09 ` john doe
2018-08-13 22:16 ` Houder
2018-08-14 9:50 ` Corinna Vinschen
2018-08-14 11:38 ` Houder
2018-08-13 20:27 ` Achim Gratz
2018-08-10 16:01 ` Marco Atzeri
2018-08-13 7:48 ` Corinna Vinschen
2018-08-13 8:36 ` Thomas Wolff [this message]
2018-08-13 11:25 ` Corinna Vinschen
2018-08-16 21:33 ` Achim Gratz
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=57db6510-86bd-3cca-5cbe-b209949ff8ea@towo.net \
--to=towo@towo.net \
--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).