Kyle Evans ef30b5a809 patch(1): Exit successfully if we're fed a 0-length patch ... This change is made in the name of GNU patch compatibility. If GNU patch is fed a zero-length patch, it will exit successfully with no output. This is used in at least one port to date (comms/wsjtx), and we break on this usage. It seems unlikely that anyone relies on patch(1) calling their completely empty patch garbage and failing, and GNU compatibility is a plus if it helps with porting, so make the switch. Reported by: db MFC after: 2 weeks		2019-03-01 01:20:21 +00:00
..
backupfile.c
backupfile.h
common.h	patch(1): Exit successfully if we're fed a 0-length patch	2019-03-01 01:20:21 +00:00
inp.c	patch(1): Don't check for NUL bytes in Plan A	2018-01-11 15:01:48 +00:00
inp.h
Makefile
Makefile.depend
mkpath.c
patch.1
patch.c	patch(1): Exit successfully if we're fed a 0-length patch	2019-03-01 01:20:21 +00:00
pathnames.h
pch.c	patch(1): Exit successfully if we're fed a 0-length patch	2019-03-01 01:20:21 +00:00
pch.h
util.c
util.h