Date: Tue, 13 Aug 2013 22:25:30 +0200 From: Matthias Andree <mandree@FreeBSD.org> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/181272: patch can't deal with blanks in filenames, GNU patch can Message-ID: <E1V9L9m-000HOX-0e@apollo.emma.line.org> Resent-Message-ID: <201308132030.r7DKU0RY000242@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 181272 >Category: bin >Synopsis: patch can't deal with blanks in filenames, GNU patch can >Confidential: no >Severity: critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Aug 13 20:30:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Matthias Andree >Release: FreeBSD 9.1-RELEASE-p5 amd64 >Organization: >Environment: System: FreeBSD apollo.emma.line.org 9.1-RELEASE-p5 FreeBSD 9.1-RELEASE-p5 #0: Sat Jul 27 01:14:23 UTC 2013 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: FreeBSD 9.1-RELEASE's /usr/bin/patch cannot handle unified patches with a blank in the filename, while GNU patch (from ports, installed as gpatch) can. Note that the filename on +++/--- lines extends from between the blank after these three characters up to the next tab character. Arguably this is nonstandard or unspecified behaviour, but then again POSIX did not specify diff's -u format until very recently; and defers to GNU diff. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1V9L9m-000HOX-0e>