Colin Percival c85ac10468 If lstat(2) fails, have bsdtar return a non-zero exit code if the ... failed path is one which was specified on the command line. This is a compromise between the situation prior to revision 1.57 (where a race between tar(1) and rm(1) could cause tar(1) to spuriously report an error) and the situation after revision 1.57 (where "tar -c /no/such/path" prints a warning but returns with an exit code of zero). Inspired by: rafan MFC after: 1 week		2007-05-03 04:33:11 +00:00
..
test	When testing basic functionality, strip trailing '/' from	2007-04-18 04:35:17 +00:00
bsdtar.1	Correct the copyright messages: Make this a standard vanilla	2007-01-09 08:12:17 +00:00
bsdtar.c	Issue a warning if there's a non-zero exit value.	2007-03-24 03:25:49 +00:00
bsdtar.h	bsdtar 2.0.23:	2007-03-11 10:36:42 +00:00
bsdtar_platform.h	Make it easier to support more platforms.	2007-04-12 04:45:32 +00:00
config_freebsd.h	bsdtar 2.0.23:	2007-03-11 10:36:42 +00:00
COPYING	Correct the copyright messages: Make this a standard vanilla	2007-01-09 08:12:17 +00:00
getdate.y	bsdtar 2.0.23:	2007-03-11 10:36:42 +00:00
Makefile	Make it easier to support more platforms.	2007-04-12 04:45:32 +00:00
matching.c	bsdtar 2.0.23:	2007-03-11 10:36:42 +00:00
read.c	In libarchive: Downgrade ARCHIVE_FATAL and ARCHIVE_FAILED errors which	2007-04-16 04:04:50 +00:00
tree.c	bsdtar 2.0.23:	2007-03-11 10:36:42 +00:00
tree.h	Correct the copyright messages: Make this a standard vanilla	2007-01-09 08:12:17 +00:00
util.c	Ignore trailing '/' when comparing pathnames, so that	2007-04-18 04:36:11 +00:00
write.c	If lstat(2) fails, have bsdtar return a non-zero exit code if the	2007-05-03 04:33:11 +00:00