From: Cygwin help2man Maintainer <Brian.Inglis@SystematicSW.ab.ca>
To: Cygwin Announcements <cygwin-announce@cygwin.com>
Subject: Updated: help2man 1.48.5
Date: Sun, 19 Sep 2021 17:15:09 -0600 [thread overview]
Message-ID: <20210919171509.37787-1-Brian.Inglis@SystematicSW.ab.ca> (raw)
The following packages have been upgraded in the Cygwin distribution:
* help2man 1.48.5
Perl script that automatically creates man pages from the
output from a program's --help and --version options.
For more information see the project home page:
https://www.gnu.org/software/help2man/
Please see below or read /usr/share/doc/help2man/NEWS after installation
for details of changes since the last Cygwin release.
Changes
1.48.5
* Use @samp{} around the option in the menu description for "--help
recommendations" to avoid rendering the -- as endash.
* Update French translations.
1.48.4
* Fix typo in comment and update some URLs to use https.
* Update Swedish translations.
1.48.3
* Don't translate @documentencoding.
* Update Serbian and Esperanto translation.
1.48.2
* Update Chinese (simplified) translation.
1.48.1
* Update German, Spanish, Norwegian Bokmaal, Polish, Brazilian
Portuguese, Russian and Ukranian translations.
* Update German, Spanish, Polish, Brazilian Portuguese and Ukranian info
page translations.
1.47.17
* Add Serbian translation of info page.
* Update Swedish translation.
1.47.16
* Move table of contents to the top of the texi file so that it appears
in the correct location in the html page.
* Update help2man.html.PL for new GNU boilerplate.
1.47.15
* Use the package name and version as the default for --source (was
program).
* Support packages in version strings without the GNU or Free prefix.
* Allow an optional second dash to separate the package name from the
version for multi-word packages: "program - package name - version".
1.47.14
* Revert --version parsing change from 1.47.13, which had unintended
consequences for some version strings. Multi-word package names are
supported only in the "program (GNU package) version" variant.
1.47.13
* Merge change from Po-Chuan Hsieh to suppress creation of an empty
pkglibdir when nls is disabled.
* Remove install_dirs target entirely, add explicit $(MKINSTALLDIRS)
before each $(INSTALL_{DATA,PROGRAM}) call.
* Update parsing of --version to allow multi-word programs when
constructing the placeholder NAME paragraph.
1.47.12
* Fix minor error in po/es.po .
* Fix ordering of "other" sections in manual page.
1.47.11
* Adjust maintainer sanity check again, this time to handle binary NMUs.
1.47.10
*
of README rather than the mtime, which may be have been modified by
dpkg-source.
1.47.9
* Add Tamil translation.
1.47.8
* Fix git repository link in generated README.
1.47.7
* Reference version-specific /usr/share/common-licenses/GPL-3 in
copyright rather than the unversioned GPL symlink.
* Add Swedish translation of info page.
1.47.6
* Update Vcs-Git/Vcs-Browser.
* Add Brazilian Portuguese translation of info page.
* Update Hungarian and Brazilian Portuguese translations.
1.47.5
* Refresh Brazilian Portuguese translation from translation project copy.
* Update Swedish translation.
* Use POSIX compliant TZ when setting UTC.
reply other threads:[~2021-09-19 23:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210919171509.37787-1-Brian.Inglis@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-announce@cygwin.com \
--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).