summaryrefslogtreecommitdiff
path: root/t/t5000
diff options
context:
space:
mode:
authorRené Scharfe <rene.scharfe@lsrfire.ath.cx>2013-05-20 09:58:29 (GMT)
committerJunio C Hamano <gitster@pobox.com>2013-05-20 22:31:46 (GMT)
commit9bf1ac41d215f9b1c026fe585a38ffa0555a5670 (patch)
tree5c7c3c9c7300dd3a6b165ee0d1a89575e10060ad /t/t5000
parent0a00ee58446e3a74e480057059a877da9c857346 (diff)
downloadgit-9bf1ac41d215f9b1c026fe585a38ffa0555a5670.zip
git-9bf1ac41d215f9b1c026fe585a38ffa0555a5670.tar.gz
git-9bf1ac41d215f9b1c026fe585a38ffa0555a5670.tar.bz2
t5000: test long filenames
Add a file with a long name to the test archive in order to check entries with pax extended headers. Also add a check for tar versions that doen't understand this format. Those versions should extract the headers as a regular files. Add code to check_tar() to interpret the path header if present, so that our tests work even with those tar versions. It's important to use the fallback code only if needed to still be able to detect git archive errorously creating pax headers as regular file entries (with a suitable tar version, of course). The archive used to check for pax header support in tar was generated using GNU tar 1.26 and its option --format=pax. Tested successfully on NetBSD 6.1, which has a tar version lacking pax header support. Signed-off-by: René Scharfe <rene.scharfe@lsrfire.ath.cx> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5000')
-rw-r--r--t/t5000/pax.tarbin0 -> 10240 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/t/t5000/pax.tar b/t/t5000/pax.tar
new file mode 100644
index 0000000..d911737
--- /dev/null
+++ b/t/t5000/pax.tar
Binary files differ