From: Andreas Gruenbacher <agruen-mXXj517/zsQ@public.gmane.org>
To: bug-patch-mXXj517/zsQ@public.gmane.org
Cc: git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: GNU patch close to next stable release
Date: Tue, 17 Apr 2012 18:07:53 +0200 [thread overview]
Message-ID: <201204171807.54771.agruen@gnu.org> (raw)
I'm glad to announce that finally, support for git-style diffs is working well
enough, and no more major issues seem to be in our way before the next stable
release of GNU patch.
Some things have changed significantly recently in order to get the code
release ready, so now would be a really great time for an extra round of
testing.
You can find the latest snapshot here:
ftp://alpha.gnu.org/gnu/patch/
The last stable release dates back to December 2009 with version 2.6.1. The
following significant changes have happened since then:
* Support for most features of the "diff --git" format, including renames and
copies, permission changes, and symlink diffs. Binary diffs are not
supported yet; patch will complain and skip them.
* Support for double-quoted filenames in the "diff --git" format: when a
filename starts with a double quote, it is interpreted as a C string
literal. The escape sequences \\, \", \a, \b, \f, \n, \r, \t, \v, and \ooo
(a three-digit octal number between 0 and 255) are recognized.
* Patch now ignores destination file names that are absolute or that contain
a component of "..". This addresses CVE-2010-4651.
* Refuse to apply a normal patch to a symlink. (Previous versions of patch
were replacing the symlink with a regular file.)
* When trying to modify a read-only file, warn about the potential problem
by default. The --read-only command line option allows to change this
behavior.
* Files that should be deleted are now deleted once the entire patch file has
been read. This fixes a bug with numbered backup files.
* When a timestamp specifies a time zone, honor that instead of assuming the
local time zone (--set-date) or Universal Coordinated Time (--set-utc).
* Support for nanosecond precision timestamps.
* Many portability and bug fixes.
Please report bugs or suggestions on the <bug-patch-mXXj517/zsQ@public.gmane.org> mailing list, or
in the project's bug tracker on Savannah:
http://savannah.gnu.org/projects/patch
Thanks,
Andreas
reply other threads:[~2012-04-17 16:08 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=201204171807.54771.agruen@gnu.org \
--to=agruen-mxxj517/zsq@public.gmane.org \
--cc=bug-patch-mXXj517/zsQ@public.gmane.org \
--cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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 NNTP newsgroup(s).