From: "Cygwin diffutils co-Maintainer" <Brian.Inglis@SystematicSW.ab.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: diffutils 3.8
Date: Fri, 06 Aug 2021 01:59:03 -0600 [thread overview]
Message-ID: <20210806015903.49655-1-Brian.Inglis@SystematicSW.ab.ca> (raw)
The following packages have been upgraded in the Cygwin distribution:
* diffutils 3.8
Diffutils includes four utilities: diff, cmp, diff3 and sdiff.
The diff command compares two files and shows the differences, line by line.
The cmp command shows the offset and line numbers where two files
differ, or can show the characters that differ between the two files.
The diff3 command shows the differences between three files. Diff3 can
be used when two people have made independent changes to a common
original; diff3 can produce a merged file that contains both sets of
changes and warnings about conflicts.
The sdiff command can be used to merge two files interactively.
For more information see the project home page:
https://www.gnu.org/software/diffutils/
Please see below or read /usr/share/doc/diffutils/NEWS after
installation for details of changes since the previous release:
https://git.savannah.gnu.org/cgit/diffutils.git/tree/NEWS
Noteworthy changes in release 3.8 (2021-08-01) [stable]
* Incompatible changes
diff no longer treats a closed stdin as representing an absent file
in usage like 'diff --new-file - foo <&-'. This feature was rarely
if ever used and was not portable to POSIX platforms that reopen
stdin on exec, such as SELinux if the process underwent an AT_SECURE
transition, or HP-UX even if not setuid.
[bug#33965 introduced in 2.8]
* Bug fixes
diff and related programs no longer get confused if stdin, stdout,
or stderr are closed. Previously, they sometimes opened files into
file descriptors 0, 1, or 2 and then mistakenly did I/O with them
that was intended for stdin, stdout, or stderr.
[bug#33965 present since "the beginning"]
cmp, diff and sdiff no longer treat negative command-line
option-arguments as if they were large positive numbers.
[bug#35256 introduced in 2.8]
Noteworthy changes in release 3.7 (2018-12-31) [stable]
* Bug fixes
diff --strip-trailing-cr with a single CR byte in one input file
would provoke an uninitialized memory read, e.g.,
diff -a --strip-trailing-cr <(printf '\r') <(echo a)
[bug introduced in 2.8 with addition of the --strip-trailing-cr option]
* Improvements
diff --color now produces output compatible with less -R.
Noteworthy changes in release 3.6 (2017-05-21) [stable]
* New features
When one file is a prefix of the other, cmp now appends the shorter
file's size to the EOF diagnostic.
* Bug fixes
Using an invalid regular expression with --ignore-matching-lines=RE (-I)
no longer causes stack overflow. Before, with an invocation like the
following, diff would diagnose the error, but would still proceed to
blow the stack: diff -Ia -I\\ <(echo) <(echo b)
[bug introduced in 2.9]
diff no longer mishandles line numbers exceeding 2**31 on Mingw-w64.
the ---presume-output-tty (ostensibly test-only) option would cause
diff --color to read an uninitialized variable
[bug introduced in 3.4]
* Performance changes
diff's default algorithm has been tweaked to deal better with larger
files, reversing some of the changes made in diffutils-3.4.
reply other threads:[~2021-08-06 8:03 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=20210806015903.49655-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).