public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Cygwin patchutils Maintainer <Brian.Inglis@SystematicSW.ab.ca>
To: Cygwin Announcements <cygwin-announce@cygwin.com>
Subject: Updated: patchutils 0.4.2
Date: Sun, 19 Sep 2021 17:18:25 -0600	[thread overview]
Message-ID: <20210919171825.40308-1-Brian.Inglis@SystematicSW.ab.ca> (raw)

The following packages have been upgraded in the Cygwin distribution:

* patchutils	0.4.2

Patchutils is a small collection of programs that operates on patch
files to list, grep, filter, split, combine, correct, or fix them.

For more information see the project home page:

	https://directory.fsf.org/wiki/Patchutils
	http://cyberelk.net/tim/software/patchutils

or the repo README:

	https://github.com/twaugh/patchutils/blob/0.4.2/README

Please see the commit log or below for details of changes since the last
Cygwin release:

	https://github.com/twaugh/patchutils/commits/0.4.2


Version 0.4.2	2020 Jul 17

* Only run xmlto once
* Update .travis.yml
* Remove deprecated sudo key. Set os to linux (which is the default).


Version 0.4.0	2020 Jul 10

* Patchview addon are 3 bash and 1 python scripts
* tools (scripts) to work under svn and git repos
* Update patchview/README.patchview
* doc/patchutils.xml with patchview
* Add two unit-tests
* Add patchview (wrap of filterdiff) to Makefile.am
  in install/uninstall rules and add the symbol link
* Add patchview in help messages.
* patchview in filterdiff.c
* Allow to compile with pcre2 library
* Fix grepdiff test
* test new grepdiff `--only-match` option
* grepdiff: add `--only-match` option
* tests: use `printf` instead of `echo -ne`
* Allow more 3 lines in headers
* Fix hunk trimming
* Add new rediff test case, currently fails
* new bootstrap (more self explained).
* Make parallel 'check' work
* interdiff: provide more context when requested
* filterdiff: always use string literal format strings
* filterdiff: Fix header output.
* Adapt tests/fullheader4/run-test and remove it from XFAIL_TESTS.
* filterdiff: Display hunk comments containing NUL
* Add test to show failure caused by NUL
* spelling fixes for patchutils
* interdiff: exit with error when whitespace damage detected
* Fix numbered output with damaged input
* Test case for numbered lines with broken input
* Update 'got' in do_convert_to_context via convert_unified_hunks_to_context
* Fix context->unified conversion
* Fix lscontext3 testcase
* New testcase: lscontext3
* Fix warning 'llen[1]' may be used uninitialized.
* Fixes all the incorrect fsf addresses
* Fix resource leaks
* Some were found by coverity, others by valgrind.
* More robust fix for fullheader3 test-case.
* New test case, fullheader3, with fix (bug #1226985).
* Change rationale is in revision control.
* Don't use LINENO environment variable if not defined.
* Don't trim pre-context for patches at end of file


                 reply	other threads:[~2021-09-19 23:20 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=20210919171825.40308-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).