Vincent Batts e46a815cbc archive/tar: fix carry-over of bytes for GNU types ... Archives produced with GNU tar can have types of TypeGNULongName and TypeGNULongLink. These fields effectively appear like two file entries in the tar archive. While golang's `archive/tar` transparently provide the file name and headers and file payload, the access to the raw bytes is still needed. This fixes the access to the longlink header, it's payload (of the long file path name), and the following file header and actual file payload.		2015-08-11 15:57:20 -04:00
..
testdata	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00
common.go	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00
example_test.go	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00
reader.go	archive/tar: fix carry-over of bytes for GNU types	2015-08-11 15:57:20 -04:00
reader_test.go	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00
stat_atim.go	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00
stat_atimespec.go	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00
stat_unix.go	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00
tar_test.go	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00
writer.go	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00
writer_test.go	archive/tar: adding from go as of a9dddb53f	2015-02-11 14:08:03 +01:00