FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F12.2 2019-12-03T18:55:09Z 2019-12-03T18:55:09Z Kyle Evans kevans@FreeBSD.org 2019-12-03T18:55:09Z urn:sha1:be3a0c5043ce6f6dd57ad55276e9b67447be6867 r351836: patch(1): add some basic tests Summary: - basic: test application of patches created by diff -u at the beginning/middle/end of file, which have differing amounts of context before and after chunks being added - limited_ctx: stems from PR 74127 in which a rogue line was getting added when the patch should have been rejected. Similar behavior was reproducible with larger contexts near the beginning/end of a file. See r326084 for details - file_creation: patch sourced from /dev/null should create the file - file_nodupe: said patch sourced from /dev/null shouldn't dupe the contents when re-applied (personal vendetta, WIP, see comment) - file_removal: this follows from nodupe; the reverse of a patch sourced from /dev/null is most naturally deleting the file, as is expected based on GNU patch behavior (WIP) r351866: patch(1): fix the file removal test, strengthen it a bit To remain compatible with GNU patch, we should ensure that once we're removing empty files after a reversed /dev/null patch we don't remove files that have been modified. GNU patch leaves these intact and just reverses the hunk that created the file, effectively implying --remove-empty-files for reversed /dev/null patches. r354328: patch(1): give /dev/null patches special treatment We have a bad habit of duplicating contents of files that are sourced from /dev/null and applied more than once... take the more sane (in most ways) GNU route and complain if the file exists and offer reversal options. This still falls short a little bit as selecting "don't reverse, apply anyway" will still give you duplicated file contents. There's probably other issues as well, but awareness is the first step to happiness. 2017-01-02T18:23:31Z Pedro F. Giffuni pfg@FreeBSD.org 2017-01-02T18:23:31Z urn:sha1:4f548c1916e86995b61b678743c91d689bba8581 patch(1): extend the maximum length of a line from USHRT_MAX to UINT_MAX. This doesn't really work for 32 bit platforms. Pointed out by: kib 2017-01-02T17:12:14Z Pedro F. Giffuni pfg@FreeBSD.org 2017-01-02T17:12:14Z urn:sha1:ad8469feec8a84469d38b4a1237fd39abea16198 We can handle such "big data" without much trouble. Try to do a better job at detecting the rejection cause while here. MFC after: 2 weeks 2014-06-15T03:54:23Z Pedro F. Giffuni pfg@FreeBSD.org 2014-06-15T03:54:23Z urn:sha1:c1a08643e3f6c6af2672fc7fd50251465f580489 Patch(1) uses a short int for the line length, which is usually sufficient for regular diffs, but makes no effort to signal when there is an overflow. Change the line length to an unsigned short int to better use the fact that a length is never negative. The change is loosely inspired on a related change in DragonFly, but we avoid spending more memory than necessary. While here adjust the messages to be clearer on what is happening. MFC after: 1 week 2014-04-21T22:52:18Z Pedro F. Giffuni pfg@FreeBSD.org 2014-04-21T22:52:18Z urn:sha1:b1a409863f4784ab8a7a9fa04b3e9b3c92e7fd72 MFC after: 3 days 2013-01-29T20:05:16Z Xin LI delphij@FreeBSD.org 2013-01-29T20:05:16Z urn:sha1:e56ef7d3586d1dea57990c7d94e260b54423ffc3 - Remove $DragonFly$ tags as they are using git nowadays and VCS tags will not help merging. - Other changes to Copyright headers to make them consistent with other source code, we intend to fork from this point. Reviewed by: pfg 2013-01-29T17:03:18Z Gabor Kovesdan gabor@FreeBSD.org 2013-01-29T17:03:18Z urn:sha1:2dd076b84bb1129d0a62b886a4e736a9344b3376 DragonflyBSD and install it as bsdpatch. WITH_BSD_PATCH makes it default and installs GNU patch as gnupatch. Submitted by: pfg Obtained from: The DragonflyBSD Project 1997-07-13T14:26:00Z Peter Wemm peter@FreeBSD.org 1997-07-13T14:26:00Z urn:sha1:65b3003d2db57c7e7f521f5f091ed7adbc151768 1997-07-06T06:54:14Z Bruce Evans bde@FreeBSD.org 1997-07-06T06:54:14Z urn:sha1:c44252b6e8da46f58fd1882b9e7305a0f9114c16 pascal and vmstat.sparc. All changed files on the vendor branch should already have been imported.