From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: libunistring 1.1-1
Date: Mon, 14 Nov 2022 14:21:44 -0700 [thread overview]
Message-ID: <d54245d1-967b-9474-88f0-afaa7332c5d2@SystematicSw.ab.ca> (raw)
In-Reply-To: <1634921335.1027198.1668432507257@kpc.webmail.kpnmail.nl>
On Mon, 14 Nov 2022 14:28:27 +0100 (CET), Erwin Waterlander wrote:
> Op 13-11-2022 22:17 CET schreef Thomas Wolff <towo@towo.net>:
>> By the way, on cygwin 32-bit the dependency does not resolve as
>> libunistring5 is not available...
> I can make it available on 32-bit, if it is still possible.
> I read that x86 is end-of-life' since Friday.
> Is it still worth the effort?
Extended by a week thanks to Jon, so please do, then I can release updated gettext.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2022-11-14 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 8:56 Error after updating gettext, missing libunistring5 Carlo B.
2022-11-13 20:43 ` [ANNOUNCEMENT] Updated: libunistring 1.1-1 Brian Inglis
2022-11-13 21:17 ` Thomas Wolff
2022-11-14 13:28 ` Erwin Waterlander
2022-11-14 13:33 ` Thomas Wolff
2022-11-14 21:21 ` Brian Inglis [this message]
2022-11-15 9:14 ` Erwin Waterlander
-- strict thread matches above, loose matches on Subject: below --
2022-10-28 6:41 Erwin Waterlander via Cygwin-announce
2022-11-12 12:50 ` 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=d54245d1-967b-9474-88f0-afaa7332c5d2@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).