From: Erwin Waterlander <waterlan@xs4all.nl>
To: cygwin-announce@cygwin.com
Subject: Updated: libpipeline-1.5.6-1
Date: Thu, 6 Oct 2022 22:45:44 +0200 (CEST) [thread overview]
Message-ID: <2007204501.991186.1665089144956@kpc.webmail.kpnmail.nl> (raw)
CHANGES
=======
libpipeline 1.5.6 (24 April 2022)
---------------------------------
Fix handling of leading whitespace in pipecmd_new_argstr and
pipecmd_argstr.
libpipeline 1.5.5 (3 January 2022)
----------------------------------
Move release process to GitLab CI.
libpipeline 1.5.4 (7 November 2021)
-----------------------------------
Move Git repository to GitLab (https://gitlab.com/cjwatson/libpipeline).
Building libpipeline now requires Autoconf >= 2.64.
https://gitlab.com/cjwatson/libpipeline/-/blob/master/NEWS.md
DESCRIPTION
===========
libpipeline is a C library for manipulating pipelines of sub-processes
in a flexible and convenient way.
See http://libpipeline.nongnu.org/
Libpipeline is required for man-db. Man-db is an alternative 'man'
package (http://man-db.nongnu.org/). Man-db is used by major Linux
distributions such as Debian, Suse, and Fedora. A big advantage of
man-db is better internationalisation support.
best regards,
--
Erwin Waterlander
http://waterlan.home.xs4all.nl/
reply other threads:[~2022-10-06 20:45 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=2007204501.991186.1665089144956@kpc.webmail.kpnmail.nl \
--to=waterlan@xs4all.nl \
--cc=cygwin-announce@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).