+2004-02-18 Sergey Poznyakoff <gray@Mirddin.farlep.net>
+
+ * README: Updated
+ * configure.ac: Added stpcpy
+ * bootstrap: Likewise
+ * lib/Makefile.am: Likewise
+ * src/common.h (xheader_xhdr_name,xheader_ghdr_name): New
+ functions
+ * src/create.c (write_extended): Call xheader_xhdr_name
+ instead of using hardcoded "././@PaxHeader" name.
+ * src/tar.c: New option --pax-option (equivalent to -o option
+ of pax).
+ * src/xheader.c: Implement pax -o option. Fixed misleading
+ heading comment (introduced 2003-09-02).
+ * src/incremen.c: Minor fixes
+ * m4/.cvsignore: Updated
+
+2004-02-17 Sergey Poznyakoff <gray@Mirddin.farlep.net>
+
+ * src/incremen.c: Removed accumulator stuff in favor of obstack.
+ (get_directory_contents): Split into two functions
+ * src/update.c: Minor changes
+ * doc/tar.texi: Fixed typo
+
+2004-02-15 Paul Eggert <eggert@twinsun.com>
+
+ Fix Debian bug 230872, originally reported by Jeff King in
+ <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=230872>.
+
+ * doc/tar.texi (posix compliance): Remove. The whole section
+ was a misunderstanding of what POSIXLY_CORRECT is supposed to
+ mean. The GNU Coding Standards says that POSIXLY_CORRECT
+ is for disabling extensions that are incompatible with POSIX:
+ it is not for disabling compatible extensions. All references
+ to this section removed.
+ (posix): This format is created only if the posix format is
+ specified; it is no longer created if gnu format is specified
+ and POSIXLY_CORRECT is set.
+ * src/tar.c (decode_options): Ignore POSIXLY_CORRECT.
+ POSIX does not specify the behavior of tar, so we should
+ not worry about POSIXLY_CORRECT here.
+