public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] icu 63.1-1
Date: Wed, 24 Oct 2018 15:33:00 -0000	[thread overview]
Message-ID: <4cd64417-2701-23cf-bc1f-9eaf12b725b3@cornell.edu> (raw)
In-Reply-To: <5656d1a4-0b58-177b-0347-15682b41d87d@weilnetz.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 988 bytes --]

On 10/22/2018 11:01 AM, Stefan Weil wrote:
> Am 22.10.2018 um 16:04 schrieb Ken Brown:
>> The following packages have been uploaded to the Cygwin distribution:
>>
>> * libicu63-63.1-1
>> * libicu-devel-63.1-1
>> * icu-doc-63.1-1
>>
> 
> What about mingw64-x86_64-icu and mingw64-i686-icu? Will they get an
> update, too? Currently they are still at 57.1-2.

Sorry, but I can only point you to my previous answer:

   http://www.cygwin.org/ml/cygwin/2018-06/msg00255.html

I suspect that Yaakov is just busy with other things.  Are you willing to take 
over as maintainer of those packages (assuming that Yaakov is willing to give 
them up)?  If so, an email to the cygwin-apps mailing list offering to do that 
would be appropriate.

Ken
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

  reply	other threads:[~2018-10-24 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 14:54 Ken Brown
2018-10-22 15:01 ` Stefan Weil
2018-10-24 15:33   ` Ken Brown [this message]
2019-04-26 19:33   ` mingw64-x86_64-icu / mingw64-i686-icu 64.2 Stefan Weil
2019-04-27  8:54     ` 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=4cd64417-2701-23cf-bc1f-9eaf12b725b3@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).