From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: [ITA] gettext
Date: Thu, 29 Jul 2021 11:50:25 -0600 [thread overview]
Message-ID: <b0315f0e-ed96-7077-1b8d-081c5b792a10@SystematicSw.ab.ca> (raw)
I'd like to adopt the following packages to get them updated to current
0.21 as prereqs to updating and adopting libidn:
gettext ORPHANED (Yaakov Selkowitz)
mingw64-x86_64-gettext ORPHANED (Yaakov Selkowitz)
mingw64-i686-gettext ORPHANED (Yaakov Selkowitz)
and possibly the following if they are still required and useful and I
can get some build problems fixed:
cygwin64-gettext ORPHANED (Yaakov Selkowitz)
cygwin32-gettext ORPHANED (Yaakov Selkowitz)
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next reply other threads:[~2021-07-29 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 17:50 Brian Inglis [this message]
2021-07-29 19:28 ` Marco Atzeri
2021-07-30 0:19 ` Brian Inglis
2021-07-30 18:21 ` Achim Gratz
2021-07-30 19:14 ` Brian Inglis
2021-08-04 13:25 ` Jon Turney
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=b0315f0e-ed96-7077-1b8d-081c5b792a10@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).