+version 1.13.11 - Paul Eggert, 1999-08-23.
+
+* The short name of the --bzip option has been changed to -I,
+ for compatibility with paxutils.
+
+* -T /dev/null now matches nothing; previously, it matched anything
+ if no explicit operands were given.
+
+* The `--' option now works the same as with other GNU utilities;
+ it causes later operands to be interpreted as file names, not options,
+ even if they begin with `-'.
+
+* For the --newer and --after-date options, the table of time zone
+ abbreviations like `EST' has been updated to match current practice.
+ Also, local time abbreviations are now recognized, even if they are
+ not in tar's hardwired table. Remember, thougy, that you should use
+ numeric UTC offsets like `-0500' instead of abbreviations like
+ `EST', as abbreviations are not standardized and are ambiguous.
+
+
+version 1.13.10 - Paul Eggert, 1999-08-20.
+
+* `tar' now uses signed base-64 when outputting header values that are
+ out of the range of the standard unsigned base-8 format. This
+ affects archive members with negative time stamps or uids, and
+ archive members 8 GB or larger. The new tar archives cannot be read
+ by traditional tar, or by older versions of GNU tar. Use the
+ --old-archive option to revert to the old behavior, which uses
+ unportable representations for negative values, and which rejects
+ large files.
+
+version 1.13.9 - Paul Eggert, 1999-08-18.
+
+* `tar' now writes two zero blocks at end-of-archive instead of just one.
+ POSIX.1 requires this, and some other `tar' implementations check for it.
+
+* `tar' no longer silently accepts a block containing nonzero checksum bytes
+ as a zero block.
+
+* `tar' now reads buggy tar files that have a null byte at the start of a
+ numeric header field.
+
+
+version 1.13.8 - Paul Eggert, 1999-08-16.
+
+* For compatibility with traditional `tar', intermediate directories
+ created automatically by root are no longer given the uid and gid of
+ the original file or directory.
+
+