NEWS 47 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229123012311232123312341235123612371238123912401241124212431244124512461247124812491250125112521253125412551256125712581259126012611262126312641265126612671268126912701271127212731274127512761277
  1. GNU tar NEWS - User visible changes. 2010-03-28
  2. Please send GNU tar bug reports to <bug-tar@gnu.org>
  3. version 1.23.90 - (Git)
  4. * The --full-time option.
  5. New command line option `--full-time' instructs tar to output file
  6. time stamps to the full resolution.
  7. * Bugfixes.
  8. ** Spurious error diagnostics on broken pipe.
  9. When receiving SIGPIPE, tar would exit with error status and
  10. "write error" diagnostics. In particular, this occurred if
  11. invoked as in the example below:
  12. tar tf archive.tar | head -n 1
  13. ** --remove-files
  14. Tar --remove-files failed to remove a directory which contained
  15. symlinks to another files within that directory.
  16. ** --test-label behavior
  17. In case of a mismatch, `tar --test-label LABEL' exits with code 1,
  18. not 2 as it did in previous versions.
  19. The `--verbose' option used with `--test-label' provides additional
  20. diagnostics.
  21. Several volume labels may be specified in a command line, e.g.:
  22. tar --test-label -f archive 'My volume' 'New volume' 'Test volume'
  23. In this case, tar exits with code 0 if any one of the arguments
  24. matches the actual volume label.
  25. ** --label used with --update
  26. The `--label' option can be used with `--update' to prevent accidental
  27. update of an archive:
  28. tar -rf archive --label 'My volume' .
  29. This did not work in previous versions, in spite of what the docs said.
  30. ** Fix dead loop on extracting existing symlinks with the -k option.
  31. version 1.23 - Sergey Poznyakoff, 2010-03-10
  32. * Record size autodetection
  33. When listing or extracting archives, the actual record size is
  34. reported only if the archive is read from a device (as opposed
  35. to regular files and pipes).
  36. * Seekable archives
  37. When a read-only operation (e.g. --list or --extract) is requested
  38. on a regular file, tar attemtps to speed up accesses by using lseek.
  39. * New command line option `--warning'
  40. The `--warning' command line option allows to suppress or enable
  41. particular warning messages during `tar' run. It takes a single
  42. argument (a `keyword'), identifying the class of warning messages
  43. to affect. If the argument is prefixed with `no-', such warning
  44. messages are suppressed. For example,
  45. tar --warning=no-alone-zero-block -x -f archive
  46. suppresses the output of `A lone zero block' diagnostics, which is
  47. normally issued if `archive' ends with a single block of zeros.
  48. See Tar Manual, section 3.9 "Controlling Warning Messages", for a
  49. detailed discussion.
  50. * New command line option `--level'
  51. The `--level=N' option sets the incremental dump level N. It
  52. is valid when used in conjunction with the -c and --listed-incremental
  53. options. So far the only meaningful value for N is 0. The
  54. `--level=0' option forces creating the level 0 dump, by truncating
  55. the snapshot file if it exists.
  56. * Files removed during incremental dumps
  57. If a file or directory is removed while incremental dump is
  58. in progress, tar exact actions depend on whether this file
  59. was explicitly listed in the command line, or was found
  60. during file system scan.
  61. If the file was explicitly listed in the command line, tar
  62. issues error message and exits with the code 2, meaning
  63. fatal error.
  64. Otherwise, if the file was found during the file system scan,
  65. tar issues a warning, saying "File removed before we read it",
  66. and sets exit code to 1, which means "some files differ".
  67. If the --warning=no-file-removed option is given, no warning
  68. is issued and exit code remains 0.
  69. * Modification times of PAX extended headers.
  70. Modification times in ustar header blocks of extended headers
  71. are set to mtimes of the corresponding archive members. This
  72. can be overridden by the
  73. --pax-opion='exthdr.mtime=STRING'
  74. command line option. The STRING is either number of seconds since
  75. the Epoch or a `Time reference' (see below).
  76. Modification times in ustar header blocks of global extended
  77. headers are set to the time when tar was invoked.
  78. This can be overridden by the
  79. --pax-opion='globexthdr.mtime=STRING'
  80. command line option. The STRING is either number of seconds since
  81. the Epoch or a `Time reference' (see below).
  82. * Time references in --pax-option argument.
  83. Any value from the --pax-option argument that is enclosed in a pair
  84. of curly braces represents a time reference. The string between the
  85. braces is understood either as a textual time representation, as described in
  86. chapter 7, "Date input formats", of the Tar manual, or as a name of
  87. an existing file, starting with `/' or `.'. In the latter
  88. case, it is replaced with the modification time of that file.
  89. * Environment of --to-command script.
  90. The environment passed to the --to-command script is extended with
  91. the following variables:
  92. TAR_VERSION GNU tar version number
  93. TAR_ARCHIVE The name of the archive
  94. TAR_VOLUME Ordinal number of the volume
  95. TAR_FORMAT Format of the archive
  96. TAR_BLOCKING_FACTOR Current blocking factor
  97. * Bugfixes
  98. ** Fix handling of hard link targets by -c --transform.
  99. ** Fix hard links recognition with -c --remove-files.
  100. ** Fix restoring files from backup (debian bug #508199).
  101. ** Correctly restore modes and permissions on existing directories.
  102. ** The --remove-files option removes files only if they were
  103. succesfully stored in the archive.
  104. ** Fix storing and listing of the volume labels in POSIX format.
  105. ** Improve algorithm for splitting long file names (ustar
  106. format).
  107. ** Fix possible memory overflow in the rmt client code (CVE-2010-0624).
  108. version 1.22 - Sergey Poznyakoff, 2009-03-05
  109. * Support for xz compression
  110. Tar uses xz for compression if one of the following conditions is met:
  111. 1. The option --xz or -J (see below) is used.
  112. 2. The xz binary is set as compressor using --use-compress-program option.
  113. 3. The file name of the archive being created ends in `.xz' and
  114. auto-compress option (-a) is used.
  115. Xz is used for decompression if one of the following conditions is met:
  116. 1. The option --xz or -J is used.
  117. 2. The xz binary is set as compressor using --use-compress-program option.
  118. 3. The file is recognized as xz compressed stream data.
  119. * Short option -J reassigned as a short equivalent of --xz
  120. * New option -I
  121. The -I option is assigned as a short equivalent for
  122. --use-compress-program.
  123. * The --no-recursive option works in incremental mode.
  124. version 1.21 - Sergey Poznyakoff, 2008-12-27
  125. * New short option -J
  126. A shortcut for --lzma.
  127. * New option --lzop
  128. * New option --no-auto-compress
  129. Cancels the effect of previous --auto-compress (-a) option.
  130. * New option --no-null
  131. Cancels the effect of previous --null option.
  132. * Compressed format recognition
  133. If tar is unable to determine archive compression format, it falls
  134. back to using archive suffix to determine it.
  135. * VCS support.
  136. Using --exclude-vcs handles also files used internally by Bazaar,
  137. Mercurial and Darcs.
  138. * Transformation scope flags
  139. Name transformation expressions understand additional flags that
  140. control type of archive members affected by them. The flags are:
  141. - r
  142. Apply transformation to regular archive members.
  143. - s
  144. Apply transformation to symbolic link targets.
  145. - h
  146. Apply transformation to hard link targets.
  147. Corresponding upper-case letters negate the meaning, so that
  148. `H' means ``do not apply transformation to hard link targets.''
  149. The scope flags are listed in the third part of an `s' expression,
  150. e.g.:
  151. tar --transform 's|^|/usr/local/|S'
  152. Default is `rsh', which means that transformations are applied to
  153. both regular archive members and to the targets of symbolic and hard
  154. links. If several transform expressions are used, the default flags
  155. can be changed using `flags=' statement before the expressions, e.g.:
  156. tar --transform 'flags=S;s|^|/usr/local/|S'
  157. * Bugfixes
  158. ** The --null option disabled handling of tar options in list files. This
  159. is fixed.
  160. ** Fixed record size autodetection. If the detected record size differs from
  161. the expected value (either default one, or the one set from the
  162. command line), tar always prints a warning if verbosity level is set
  163. to 1 or greater, i.e. if either -t or -v option is given.
  164. version 1.20 - Sergey Poznyakoff, 2008-04-14
  165. * New option --auto-compress (-a)
  166. With --create, selects compression algorithm basing on the suffix
  167. of the archive file name.
  168. * New option --lzma
  169. Selects LZMA compression algorithm
  170. * New option --hard-dereference
  171. During archive creation, dereferences hard links and stores the files
  172. they refer to, instead of creating usual hard link members (type '1').
  173. * New option --checkpoint-action
  174. This action allows to specify an action to be executed upon hitting a
  175. checkpoint. Recognized actions are: dot, echo (the default),
  176. echo=string, ttyout=string, exec=cmdline, and sleep=value. Any number
  177. of `--checkpoint-action' options can be specified, the actions will be
  178. executed in order of their appearance in the command line. See
  179. chapter 3.8 "Checkpoints" for a complete description.
  180. * New options --no-check-device, --check-device.
  181. The `--no-check-device' option disables comparing device numbers during
  182. preparatory stage of an incremental dump. This allows to avoid
  183. creating full dumps if the device numbers change (e.g. when using an
  184. LVM snapshot).
  185. The `--check-device' option enables comparing device numbers. This is
  186. the default. This option is provided to undo the effect of the previous
  187. `--no-check-device' option, e.g. if it was set in TAR_OPTIONS
  188. environment variable.
  189. * The --transform option.
  190. Any number of `--transform' options can be given in the command line.
  191. The specified transformations will be applied in turn.
  192. The argument to `--transform' option can be a list of replace
  193. expressions, separated by a semicolon (as in `sed').
  194. Filename transformations are applied to symbolic link targets
  195. during both creation and extraction. Tar 1.19 used them only
  196. during extraction.
  197. For a detailed description, see chapter 6.7 "Modifying File and Member
  198. Names".
  199. * Info (end-of-volume) scripts
  200. The value of the blocking factor is made available to info and
  201. checkpoint scripts via environment variable TAR_BLOCKING_FACTOR.
  202. * Incremental archives
  203. Improved (sped up) extracting from incremental archives.
  204. * Bugfixes.
  205. ** Fix bug introduced in version 1.19: tar refused to update non-existing
  206. archives.
  207. version 1.19 - Sergey Poznyakoff, 2007-10-10
  208. * New option --exclude-vcs
  209. Excludes directories and files, created by several widely used version
  210. control systems, e.g. "CVS/", ".svn/", etc.
  211. * --exclude-tag and --exclude-cache options
  212. The following options now work with incremental archives as well:
  213. --exclude-caches
  214. --exclude-caches-all
  215. --exclude-tag
  216. --exclude-tag-all
  217. --exclude-tag-under
  218. * Fix handling of renamed files in listed incremental archives.
  219. Previous versions always stored absolute file names in rename
  220. records, even if -P was not used. This is fixed: rename records
  221. contain file names processed in accordance with the command line
  222. settings.
  223. * Fix --version output.
  224. * Recognition of broken archives.
  225. When supplied an archive smaller than 512 bytes in reading mode (-x,
  226. -t), the previous version of tar silently ignored it, exiting with
  227. code 0. It is fixed. Tar now issues the following diagnostic message:
  228. 'This does not look like a tar archive', and exits with code 2.
  229. * Fix double-dot recognition in archive member names in case of duplicate '/.'.
  230. * Fix file padding in case of truncation of the input file to zero size.
  231. version 1.18 - Sergey Poznyakoff, 2007-06-29
  232. * Licensed under the GPLv3
  233. * Fixed several bugs in the testsuite
  234. version 1.17 - Sergey Poznyakoff, 2007-06-08
  235. * Fix archivation of sparse files in posix mode. Previous versions padded
  236. sparse members with spurious zero blocks.
  237. * Fix operation of --verify --listed-incremental. Version 1.16.1 produced
  238. a full dump when both options were given.
  239. * Fix --occurrence. In previous versions it continued scanning the archive
  240. even though all requested members has already been extracted.
  241. * Scope of --transform and --strip-components options.
  242. In addition to affecting regular archive members, the --transform
  243. option affects hard and soft link targets and the --strip-components
  244. option affects hard link targets as well.
  245. * End-of-volume script can send the new volume name to tar by writing
  246. it to the file descriptor stored in the environment variable `TAR_FD'.
  247. version 1.16.1 - Sergey Poznyakoff, 2006-12-09
  248. * New option --exclude-tag allows to specify "exclusion tag files", i.e.
  249. files whose presence in a directory means that the directory should not
  250. be archived.
  251. * The --exclude-cache option excludes directories that contain the
  252. CACHEDIR.TAG file from being archived. Previous versions excluded
  253. directory contents only, while the directories themselves were
  254. still added to the archive.
  255. * Support for reading ustar type 'N' header logical records has been removed.
  256. This GNU extension was generated only by very old versions of GNU 'tar'.
  257. Unfortunately its implementation had security holes; see
  258. <http://archives.neohapsis.com/archives/fulldisclosure/2006-11/0344.html>.
  259. We don't expect that any tar archives in practical use have type 'N'
  260. records, but if you have one and you trust its contents, you can
  261. decode it with GNU tar 1.16 or earlier.
  262. * Race conditions have been fixed that in some cases briefly allowed
  263. files extracted by 'tar -x --same-owner' (or plain 'tar -x', when
  264. running as root) to be accessed by users that they shouldn't have been.
  265. version 1.16 - Sergey Poznyakoff, 2006-10-21
  266. * After creating an archive, tar exits with code 1 if some files were
  267. changed while being read. Previous versions exited with code 2 (fatal
  268. error), and only if some files were truncated while being archived.
  269. * New option --mtime allows to set modification times for all archive
  270. members during creation.
  271. * Bug fixes
  272. ** Avoid running off file descriptors when using multiple -C options.
  273. ** tar --index-file=FILE --file=- sent the archive to FILE, and
  274. the listing to stderr.
  275. version 1.15.91 - Sergey Poznyakoff, 2006-06-16
  276. * Incompatible changes
  277. ** Globbing
  278. Previous versions of GNU tar assumed shell-style globbing when
  279. extracting from or listing an archive. For example:
  280. tar xf foo.tar '*.c'
  281. would extract all files whose names end in '.c'. This behavior
  282. was not documented and was incompatible with traditional tar
  283. implementations. Therefore, starting from this version, GNU tar
  284. no longer uses globbing by default. For example, the above invocation
  285. is now interpreted as a request to extract from the archive the file
  286. named '*.c'.
  287. To treat member names as globbing patterns, use --wildcards option.
  288. If you wish tar to mimic the behavior of versions up to 1.15.90,
  289. add --wildcards to the value of the environment variable TAR_OPTIONS.
  290. The exact way in which tar interprets member names is controlled by the
  291. following command line options:
  292. --wildcards use wildcards
  293. --anchored patterns match file name start
  294. --ignore-case ignore case
  295. --wildcards-match-slash wildcards match `/'
  296. Each of these options has a '--no-' counterpart that disables its
  297. effect (e.g. --no-wildcards).
  298. These options affect both the interpretation of member names from
  299. command line and that of the exclusion patterns (given with --exclude
  300. and --exclude-from options). The defaults are:
  301. 1. For member names: --no-wildcards --anchored
  302. 2. For exclusion patterns: --wildcards --no-anchored --wildcards-match-slash
  303. The options can appear multiple times in the command line, thereby
  304. changing the way command line arguments are interpreted. For example,
  305. to use case-insensitive matching in exclude patterns and to revert to
  306. case-sensitive matching for the rest of command line, one could write:
  307. tar xf foo.tar --ignore-case --exclude-from=FILE --no-ignore-case file.name
  308. ** Short option -l is now an alias of --check-links option, which complies
  309. with UNIX98. This ends the transition period started with version 1.14.
  310. * New features
  311. ** New option --transform allows to transform file names before storing them
  312. in the archive or member names before extracting. The option takes a
  313. sed replace expression as its argument. For example,
  314. tar cf foo.tar --transform 's,^,prefix/,'
  315. will add 'prefix/' to all file names stored in foo.tar.
  316. ** --strip-components option works when deleting and comparing. In previous
  317. versions it worked only with --extract.
  318. ** New option --show-transformed-names enables display of transformed file
  319. or archive. It generalizes --show-stored-names option, introduced in
  320. 1.15.90. In particular, when creating an archive in verbose mode, it lists
  321. member names as stored in the archive, i.e., with any eventual prefixes
  322. removed and file name transformations applied. The option is useful,
  323. for example, while comparing `tar cv' and `tar tv' outputs.
  324. ** New incremental snapshot file format keeps information about file names
  325. as well as that about directories.
  326. ** The --checkpoint option takes an optional argument specifying the number
  327. of records between the two successive checkpoints. Optional dot
  328. starting the argument intructs tar to print dots instead of textual
  329. checkpoints.
  330. ** The --totals option can be used with any tar operation (previous versions
  331. understood it only with --create). If an argument to this option is
  332. given, it specifies the signal upon delivery of which the statistics
  333. is to be printed. Both forms of this option (with and without
  334. argument) can be given to in a single invocation of tar.
  335. * Bug fixes
  336. ** Detect attempts to update compressed archives.
  337. version 1.15.90 - Sergey Poznyakoff, 2006-02-19
  338. * New features
  339. ** Any number of -T (--files-from) options may be used in the command line.
  340. The file specified with -T may include any valid `tar' options,
  341. including another -T option.
  342. Compatibility note: older versions of tar would only recognize -C
  343. as an option name within the file list file. Now any file whose name
  344. starts with - is handled as an option. To insert file names starting with
  345. dash, use the --add-file option.
  346. ** List files containing null-separated file names are detected and processed
  347. automatically. It is no longer necessary to give the --null option.
  348. ** New option --no-unquote disables the unquoting of input file names.
  349. This is useful for processing output from `find dir -print0'.
  350. An orthogonal option --unquote is provided as well.
  351. ** New option --test-label tests the archive volume label.
  352. If an argument is specified, the label is compared against its value.
  353. Tar exits with code 0 if the two strings match, and with code 2 if
  354. they do not.
  355. If no argument is given, the --verbose option is implied. In this case,
  356. tar prints the label name if present and exits with code 0.
  357. ** New option --show-stored-names. When creating an archive in verbose mode,
  358. it lists member names as stored in the archive, i.e., with any eventual
  359. prefixes removed. The option is useful, for example, while comparing
  360. `tar cv' and `tar tv' outputs.
  361. ** New option --to-command pipes the contents of archive members to the
  362. specified command.
  363. ** New option --atime-preserve=system, which uses the O_NOATIME feature
  364. of recent Linux kernels to avoid some problems when preserving file
  365. access times.
  366. ** New option --delay-directory-restore delays restoring modification times
  367. and permissions of extracted directories until the end of extraction.
  368. This is necessary for restoring from archives with unusual member
  369. ordering (in particular, those created with --no-recursion option).
  370. This option is implied when restoring from incremental archives.
  371. ** New option --restrict prohibits use of some potentially harmful tar
  372. options. Currently it disables '!' escape in multi-volume name menu.
  373. ** New options --quoting-style and --quote-chars control the way tar
  374. quotes member names on output. The --quoting-style takes an argument
  375. specifying the quoting style to use (literal, shell, shell-always,
  376. c, escape, locale, clocale). The argument to --quote-chars is a string
  377. specifying characters to quote, even if the selected quoting style
  378. would not quote them otherwise. The option --no-quote-chars is
  379. provided to disable quoting certain characters.
  380. ** The end-of-volume script (introduced with --info-script option) can
  381. get current archive name from the environment variable TAR_ARCHIVE and
  382. the volume number from the variable TAR_VOLUME. It can alter the
  383. archive name by writing new name to the file descriptor 3.
  384. ** Better support for full-resolution time stamps. Tar cannot restore
  385. time stamps to full nanosecond resolution, though, until the kernel
  386. guys get their act together and give us a system call to set file time
  387. stamps to nanosecond resolution.
  388. ** The -v option now prints time stamps only to 1-minute resolution,
  389. not full resolution, to avoid using up too many output columns.
  390. Nanosecond resolution is now supported, but that would be too much.
  391. * Bug fixes
  392. ** Allow non-option arguments to be interspersed with options.
  393. ** When extracting or listing archives in old GNU format, tar
  394. used to read an extra block of data after a long name header
  395. if length of the member name was divisible by block size (512).
  396. Consequently, the file pointer was set off and the next member
  397. was not processed correctly.
  398. ** Previous version created invalid archives when files shrink
  399. during reading.
  400. ** Compare mode (tar d) hung when trying to compare file contents.
  401. ** Previous versions in certain cases failed to restore directory
  402. modification times.
  403. ** When creating an archive, do not attempt to store files whose
  404. meta-data cannot be stored in the header due to format limitations
  405. (for ustar and v7 formats).
  406. ** The --version option now also outputs information about copyright,
  407. license, and credits. This reverts to the behavior of tar 1.14 and
  408. earlier, and conforms to the GNU coding standards. The --license (-L)
  409. option introduced in tar 1.15 has been removed, since it's no longer
  410. needed.
  411. version 1.15.1 - Sergey Poznyakoff, 2004-12-21
  412. This version fixes a bug introduced in 1.15 which caused
  413. tar to refuse to extract files from standard input.
  414. version 1.15 - Sergey Poznyakoff, 2004-12-20
  415. * Compressed archives are recognised automatically, it is no longer
  416. necessary to specify -Z, -z, or -j options to read them. Thus, you can
  417. now run `tar tf archive.tar.gz'.
  418. * When restoring incremental dumps, --one-file-system option
  419. prevents directory hierarchies residing on different devices
  420. from being purged.
  421. With the previous versions of tar it was dangerous to create
  422. incremental dumps with --one-file-system option, since they
  423. would recursively remove mount points when restoring from the
  424. back up. This change fixes the bug.
  425. * Renamed --strip-path to --strip-components for consistency with
  426. the GNU convention.
  427. * Skipping archive members is sped up if the archive media supports
  428. seeks.
  429. * Restore script starts restoring only if it is given --all (-a) option,
  430. or some patterns. This is to prevent accidental restores.
  431. * `tar --verify' prints a warning if during archive creation some of
  432. the file names had their prefixes stripped off.
  433. * New option --exclude-caches instructs tar to exclude cache directories
  434. automatically on archive creation. Cache directories are those
  435. containing a standardized tag file, as specified at:
  436. http://www.brynosaurus.com/cachedir/spec.html
  437. * New configure option --with-rmt allows to specify full path name to
  438. the `rmt' utility. This supersedes DEFAULT_RMT_COMMAND variable
  439. introduced in version 1.14
  440. * New configure variable DEFAULT_RMT_DIR allows to specify the directory
  441. where to install `rmt' utility. This is necessary since modifying
  442. --libexecdir as was suggested for version 1.14 produced a side effect: it
  443. also modified installation prefix for backup scripts (if
  444. --enable-backup-scripts was given).
  445. * Bug fixes:
  446. ** Fixed flow in recognizing files to be included in incremental dumps.
  447. ** Correctly recognize sparse archive members when used with -T option.
  448. ** GNU multivolume headers cannot store filenames longer than 100 characters.
  449. Do not allow multivolume archives to begin with such filenames.
  450. ** If a member with link count > 2 was stored in the archive twice,
  451. previous versions of tar were not able to extract it, since they
  452. were trying to link the file to itself, which always failed and
  453. lead to removing the already extracted copy. Preserve the first
  454. extracted copy in such cases.
  455. ** Restore script was passing improper argument to tar --listed option (which
  456. didn't affect the functionality, but was logically incorrect).
  457. ** Fixed verification of created archives.
  458. ** Fixed unquoting of file names containing backslash escapes (previous
  459. versions failed to recognize \a and \v).
  460. ** When attempting to delete a non-existing member from the archive, previous
  461. versions of tar used to overwrite last archive block with zeroes.
  462. version 1.14 - Sergey Poznyakoff, 2004-05-11
  463. * Added support for POSIX.1-2001 and ustar archive formats.
  464. * New option --format allows to select the output archive format
  465. * The default output format can be selected at configuration time
  466. by presetting the environment variable DEFAULT_ARCHIVE_FORMAT.
  467. Allowed values are GNU, V7, OLDGNU and POSIX.
  468. * New option --strip-path allows to cut off a given number of
  469. path elements from the name of the file being extracted.
  470. * New options --index-file, --no-overwrite-dir. The --overwrite-dir
  471. option is now the default; use --no-overwrite-dir if you prefer
  472. the previous default behavior.
  473. * The semantics of -o option is changed. When extracting, it
  474. does the same as --no-same-owner GNU tar option. This is compatible
  475. with UNIX98 tar. Otherwise, its effect is the same as that of
  476. --old-archive option. This latter is deprecated and will be removed
  477. in future.
  478. * New option --check-links prints a message if not all links are dumped
  479. for a file being archived. This corresponds to the UNIX98 -l option.
  480. The current semantics of the -l option is retained for compatibility
  481. with previous releases, however such usage is strongly deprecated as
  482. the option will change to its UNIX98 semantics in the future releases.
  483. * New option --occurrence[=N] can be used in conjunction with one of
  484. the subcommands --delete, --diff, --extract or --list when a list of
  485. files is given either on the command line or via -T option. This
  486. option instructs tar to process only the Nth occurrence of each named
  487. file. N defaults to 1, so `tar -x -f archive --occurrence filename'
  488. extracts the first occurrence of `filename' from `archive'
  489. and terminates without scanning to the end of the archive.
  490. * New option --pax-option allows to control the handling of POSIX
  491. keywords in `pax' extended headers. It is equivalent to `pax'
  492. -o option.
  493. * --incremental and --listed-incremental options work correctly on
  494. individual files, as well as on directories.
  495. * New scripts: backup (replaces old level-0 and level-1) and restore.
  496. The scripts are compiled and installed if --enable-backup-scripts
  497. option is given to configure.
  498. * By default tar searches "rmt" utility in "$prefix/libexec/rmt",
  499. which is consistent with the location where the version of "rmt"
  500. included in the package is installed. Previous versions of tar
  501. used "/etc/rmt". To install "rmt" to its traditional location,
  502. run configure with option --libexecdir=/etc. Otherwise, if you
  503. already have rmt installed and wish to use it, instead of the
  504. shipped in version, set the variable DEFAULT_RMT_COMMAND to
  505. the full path name of the utility, e.g., ./configure
  506. DEFAULT_RMT_COMMAND=/etc/rmt.
  507. Notice also that the full path name of the "rmt" utility to
  508. use can be set at runtime, by giving option --rmt-command to
  509. tar.
  510. * Removed obsolete command line options:
  511. ** --absolute-paths superseded by --absolute-names
  512. ** --block-compress is not needed any longer
  513. ** --block-size superseded by --blocking-factor
  514. ** --modification-time superseded by --touch
  515. ** --read-full-blocks superseded by --read-full-records
  516. ** --record-number superseded by --block-number
  517. ** --version-control superseded by --backup
  518. * New message translations fi (Finnish), gl (Galician), hr (Croatian),
  519. hu (Hungarian), ms (Malaysian), nb (Norwegian), ro (Romanian), sk
  520. (Slovak), zh_CN (Chinese simplified), zh_TW (Chinese traditional).
  521. The code 'no' for Norwegian (Bokmål) has been withdrawn; use 'nb' instead.
  522. * Bug fixes.
  523. version 1.13.25 - Paul Eggert, 2001-09-26
  524. * Bug fixes.
  525. version 1.13.24 - Paul Eggert, 2001-09-22
  526. * New option --overwrite-dir.
  527. * Fixes for buffer overrun, porting, and copyright notice problems.
  528. * The message translations for Korean are available again.
  529. version 1.13.23 - Paul Eggert, 2001-09-13
  530. * Bug, porting, and copyright notice fixes.
  531. version 1.13.22 - Paul Eggert, 2001-08-29
  532. * Bug fixes.
  533. version 1.13.21 - Paul Eggert, 2001-08-28
  534. * Porting and copyright notice fixes.
  535. version 1.13.20 - Paul Eggert, 2001-08-27
  536. * Some bugs were fixed:
  537. - security problems
  538. - hard links to symbolic links
  539. * New option --recursion (the default) that is the inverse of --no-recursion.
  540. * New options --anchored, --ignore-case, --wildcards,
  541. --wildcards-match-slash, and their negations (e.g., --no-anchored).
  542. Along with --recursion and --no-recursion, these options control how
  543. exclude patterns are interpreted.
  544. * The default interpretation of exclude patterns is now --no-anchored
  545. --no-ignore-case --recursion --wildcards --wildcards-match-slash.
  546. This is a quiet change to the semantics of --exclude. The previous
  547. semantics were a failed attempt at backward compatibility but it
  548. became clear that the semantics were puzzling and did not satisfy
  549. everybody. Rather than continue to try to revive that dead horse we
  550. thought it better to substitute cleaner semantics, with options so
  551. that you can change the behavior more to your liking.
  552. * New message translations for Indonesian and Turkish.
  553. The translation for Korean has been withdrawn due to encoding errors.
  554. It will be reissued once those are fixed.
  555. version 1.13.19 - Paul Eggert, 2001-01-13
  556. * The -I option has been withdrawn, as it was buggy and confusing.
  557. Eventually it is planned to be reintroduced, with the same meaning as -T.
  558. * With an option like -N DATE, if DATE starts with "/" or ".", it is taken
  559. to be a file name; the last-modified time of that file is used as the date.
  560. version 1.13.18 - Paul Eggert, 2000-10-29
  561. * Some security problems have been fixed. `tar -x' now modifies only
  562. files under the working directory, unless you also specify an unsafe
  563. option like --absolute-names or --overwrite.
  564. * The short name of the --bzip option has been changed to -j,
  565. and -I is now an alias for -T, for compatibility with Solaris tar.
  566. * The manual is now distributed under the GNU Free Documentation License.
  567. * The new environment variable TAR_OPTIONS holds default command-line options.
  568. * The --no-recursion option now affects extraction too.
  569. * The wording in some diagnostics has been changed slightly.
  570. * Snapshot files now record whether each file was accessed via NFS.
  571. The new file format is upward- and downward-compatible with the old.
  572. * New language supported: da.
  573. * Compilation by traditional (K&R) C compilers is no longer supported.
  574. If you still use such a compiler, please use GCC instead.
  575. * This version of tar works best with GNU gzip test version 1.3 or later.
  576. Please see <ftp://alpha.gnu.org/gnu/gzip/>.
  577. * `tar --delete -f -' now works again.
  578. version 1.13.17 - Paul Eggert, 2000-01-07.
  579. * `tar --delete -f -' is no longer allowed; it was too buggy.
  580. * Diagnostic messages have been made more regular and consistent.
  581. version 1.13.16 - Paul Eggert, 1999-12-13.
  582. * By default, tar now refuses to overwrite an existing file when
  583. extracting files from an archive; instead, it removes the file
  584. before extracting it. If the existing file is a symbolic link, the
  585. link is removed and not the pointed-to file. There is one
  586. exception: existing nonempty directories are not removed, nor are
  587. their ownerships or permissions extracted. This fixes some
  588. longstanding security problems.
  589. The new --overwrite option enables the old default behavior.
  590. For regular files, tar implements this change by using the O_EXCL
  591. option of `open' to ensure that it creates the file; if this fails, it
  592. removes the file and tries again. This is similar to the behavior of
  593. the --unlink-first option, but it is faster in the common case of
  594. extracting a new directory.
  595. * By default, tar now ignores file names containing a component of `..'
  596. when extracting, and warns about such file names when creating an archive.
  597. To enable the old behavior, use the -P or --absolute-names option.
  598. * Tar now handles file names with multibyte encodings (e.g., UTF-8, Shift-JIS)
  599. correctly. It relies on the mbrtowc function to handle multibyte characters.
  600. * The file generated by -g or --listed-incremental now uses a format
  601. that is independent of locale, so that users need not worry about
  602. locale when restoring a backup. This is needed for proper support
  603. of multibyte characters. Old-format files can still be read, and
  604. older versions of GNU tar can read new-format files, unless member
  605. names have multibyte chars.
  606. * Many diagnostics have been changed slightly, so that file names are
  607. now output unambiguously. File names in diagnostics now are either
  608. `quoted like this' (in the default C locale) or are followed by
  609. colon, newline, or space, depending on context. Unprintable
  610. characters are escaped with a C-like backslash conventions.
  611. Terminating characters (e.g., close-quote, colon, newline)
  612. are also escaped as needed.
  613. * tar now ignores socket files when creating an archive.
  614. Previously tar archived sockets as fifos, which caused problems.
  615. version 1.13.15 - Paul Eggert, 1999-12-03.
  616. * If a file's ctime changes when being archived, report an error.
  617. Previously tar looked at mtime, which missed some errors.
  618. version 1.13.14 - Paul Eggert, 1999-11-07.
  619. * New translations ja, pt_BR.
  620. * New options --help and --version for rmt.
  621. * Ignore Solaris door files when creating an archive.
  622. version 1.13.13 - Paul Eggert, 1999-10-11.
  623. * Invalid headers in tar files now elicit errors, not just warnings.
  624. * `tar --version' output conforms to the latest GNU coding standards.
  625. * If you specify an invalid date, `tar' now substitutes (time_t) -1.
  626. * `configure --with-dmalloc' is no longer available.
  627. version 1.13.12 - Paul Eggert, 1999-09-24.
  628. * `tar' now supports hard links to symbolic links.
  629. * New options --no-same-owner, --no-same-permissions.
  630. * --total now also outputs a human-readable size, and a throughput value.
  631. * `tar' now uses two's-complement base-256 when outputting header
  632. values that are out of the range of the standard unsigned base-8
  633. format. This affects archive members with negative or huge time
  634. stamps or uids, and archive members 8 GB or larger. The new tar
  635. archives cannot be read by traditional tar, or by older versions of
  636. GNU tar. Use the --old-archive option to revert to the old
  637. behavior, which uses unportable representations for negative values,
  638. and which rejects large files.
  639. * On 32-bit hosts, `tar' now assumes that an incoming time stamp T in
  640. the range 2**31 <= T < 2**32 represents the negative time (T -
  641. 2**32). This behavior is nonstandard and is not portable to 64-bit
  642. time_t hosts, so `tar' issues a warning.
  643. * `tar' no longer gives up extracting immediately upon discovering
  644. that an archive contains garbage at the end. It attempts to extract
  645. as many files as possible from the good data before the garbage.
  646. * A read error now causes a nonzero exit status, not just a warning.
  647. * Some diagnostics have been reworded for consistency.
  648. version 1.13.11 - Paul Eggert, 1999-08-23.
  649. * The short name of the --bzip option has been changed to -I,
  650. for compatibility with paxutils.
  651. * -T /dev/null now matches nothing; previously, it matched anything
  652. if no explicit operands were given.
  653. * The `--' option now works the same as with other GNU utilities;
  654. it causes later operands to be interpreted as file names, not options,
  655. even if they begin with `-'.
  656. * For the --newer and --after-date options, the table of time zone
  657. abbreviations like `EST' has been updated to match current practice.
  658. Also, local time abbreviations are now recognized, even if they are
  659. not in tar's hardwired table. Remember, though, that you should use
  660. numeric UTC offsets like `-0500' instead of abbreviations like
  661. `EST', as abbreviations are not standardized and are ambiguous.
  662. version 1.13.10 - Paul Eggert, 1999-08-20.
  663. * `tar' now uses signed base-64 when outputting header values that are
  664. out of the range of the standard unsigned base-8 format. [This
  665. change was superseded in 1.13.12, described above.]
  666. version 1.13.9 - Paul Eggert, 1999-08-18.
  667. * `tar' now writes two zero blocks at end-of-archive instead of just one.
  668. POSIX.1 requires this, and some other `tar' implementations check for it.
  669. * `tar' no longer silently accepts a block containing nonzero checksum bytes
  670. as a zero block.
  671. * `tar' now reads buggy tar files that have a null byte at the start of a
  672. numeric header field.
  673. version 1.13.8 - Paul Eggert, 1999-08-16.
  674. * For compatibility with traditional `tar', intermediate directories
  675. created automatically by root are no longer given the uid and gid of
  676. the original file or directory.
  677. version 1.13.7 - Paul Eggert, 1999-08-14.
  678. * --listed-incremental and --newer are now incompatible options.
  679. * When creating an archive, leading `./' is no longer stripped,
  680. to match traditional tar's behavior (and simplify the documentation).
  681. * --diff without --absolute-names no longer falls back on absolute names.
  682. version 1.13.6 - Paul Eggert, 1999-08-11.
  683. * An --exclude pattern containing / now excludes a file only if it matches an
  684. initial prefix of the file name; a pattern without / continues to
  685. exclude a file if it matches any file name component.
  686. * The protocol for talking to rmt has been extended slightly.
  687. Open flags are now communicated in symbolic format as well as numeric.
  688. The symbolic format (e.g., "O_WRONLY|O_CREAT|O_TRUNC") is for portability
  689. when rmt is operating on a different operating system from tar.
  690. The numeric format is retained, and rmt uses it if symbolic format is absent,
  691. for backward compatibility with older versions of tar and rmt.
  692. * When writing GNU tar format headers, tar now uses signed base-64
  693. for values that cannot be represented in unsigned octal.
  694. This supports larger files (2**66 - 1 bytes instead of 2**33 - 1 bytes),
  695. larger uids, negative time stamps, etc.
  696. * When extracting files with unknown ownership, tar now looks up the
  697. uid and gid "nobody" on hosts whose headers do not define UID_NOBODY
  698. and GID_NOBODY, and falls back on uid/gid -2 if there is no "nobody".
  699. * tar -t --numeric-owner now prints numeric uids and gids, not symbolic.
  700. * New option -y or --bzip2 for bzip2 compression, by popular request.
  701. version 1.13.5 - Paul Eggert, 1999-07-20.
  702. * Do the delayed updates of file metadata even after a fatal error.
  703. version 1.13.4 - Paul Eggert, 1999-07-20.
  704. * Do not chmod unless we are root or the -p option was given;
  705. this matches historical practice.
  706. version 1.13.3 - Paul Eggert, 1999-07-16.
  707. * A path name is excluded if any of its file name components matches an
  708. excluded pattern, even if the path name was specified on the command line.
  709. Also see 1.13.6 for later changes in this area.
  710. version 1.13.2 - Paul Eggert, 1999-07-14.
  711. * Bug reporting address changed to <bug-tar@gnu.org>.
  712. version 1.13.1 - Paul Eggert, 1999-07-12.
  713. * Bug fixes only.
  714. version 1.13 - Paul Eggert, 1999-07-08.
  715. * Support for large files, e.g., files larger than 2 GB on many 32-bit hosts.
  716. Also, support for larger uids, device ids, etc.
  717. * Many bug fixes and porting fixes.
  718. * This release is only for fixes. A more ambitious test release,
  719. with new features, is available as part of the paxutils. Please see:
  720. ftp://alpha.gnu.org/gnu/paxutils/
  721. The fixes in this release are intended to be merged with paxutils
  722. at some point, but they haven't been merged yet.
  723. * An interim GNU tar alpha had new --bzip2 and --ending-file options,
  724. but they have been removed to maintain compatibility with paxutils.
  725. Please try --use=bzip2 instead of --bzip2.
  726. Version 1.12 - François Pinard, 1997-04.
  727. Sensitive matters
  728. * Use shell globbing patterns for --label, instead of regular expressions.
  729. * Do not quote anymore internally over the quoting done by the shell.
  730. Output for humans
  731. * Offer internationalization capabilities of most recent GNU gettext.
  732. * Messages available in many more languages, thanks to all translators!
  733. * Usage of ISO 8601 dates in listings, instead of local American dates.
  734. * More normalization and cleanup in error messages.
  735. Creation
  736. * For helping using tar with find, offer a --no-recursion option.
  737. * Implement --numeric-owner for ignoring symbolic names at create time.
  738. * New --owner, --group --mode options, still preliminary.
  739. * Recognize creating an archive on /dev/null, so Amanda works faster.
  740. * Object to the creation of an empty archive (like in `tar cf FILE').
  741. * Barely start implementing --posix and POSIXLY_CORRECT.
  742. Extraction
  743. * Make a better job at restoring file and directory attributes.
  744. * Automatically attempt deleting existing files when in the way.
  745. * Option --unlink-first (-U) removes most files prior to extraction.
  746. * Option --recursive-unlink removes non-empty directories when in the way.
  747. * Option --numeric-owner ignores owner/group names, it uses UID/GID instead.
  748. * Use global umask when creating missing intermediate directories.
  749. * When symlinks are not available, extract symbolic links as hard links.
  750. * Diagnose extraction of contiguous files as regular files.
  751. * New --backup, --suffix and --version-control options.
  752. Various changes
  753. * Better support of huge archives with --tape-length and --totals.
  754. * Rename option --read-full-blocks (-B) to --read-full-records (-B).
  755. * Rename option --block-size (-b) to --blocking-factor (-b).
  756. * Rename option --record-number (-R) to --block-number (-R).
  757. * With --block-number (-R), report null blocks and end of file.
  758. * Implement --record-size for introducing a size in bytes.
  759. * Delete --block-compress option and rather decide it automatically.
  760. * Rename option --modification-time to --touch.
  761. Many bugs are squashed, while others still run free.
  762. Version 1.11.8 - François Pinard, 1995-06.
  763. * Messages available in French, German, Portuguese and Swedish.
  764. * The distribution provides a rudimentary Texinfo manual.
  765. * The device defaults to stdin/stdout, unless overridden by the installer.
  766. * Option --sparse (-S) should work on more systems.
  767. * Option --rsh-command may select an alternative remote shell program.
  768. Most changes are internal, and should yield better portability.
  769. Version 1.11.2 - Michael Bushnell, 1993-03.
  770. * Changes in backup scripts: cleaned up considerably; notices error
  771. conditions better over rsh; DUMP_REMIND_SCRIPT is now an option in
  772. backup-specs; new file dump-remind is an example of a
  773. DUMP_REMIND_SCRIPT.
  774. * Superfluous "Reading dirname" was a bug; fixed.
  775. * Incompatibility problems with a bug on Solaris are fixed.
  776. * New option --gzip (aliases are --ungzip and -z); calls gzip instead
  777. of compress. Also, --use-compress-program lets you specify any
  778. compress program. --compress-block is renamed --block-compress and
  779. now requires one of the three compression options to be specified.
  780. * Several error messages are cleaned up.
  781. * Directory owners are now set properly when running as root.
  782. * Provide DUMP_REMIND_SCRIPT in backup-specs as a possible option
  783. for --info-script.
  784. * Behave better with broken rmt servers.
  785. * Dump scripts no longer use --atime-preserve; this causes a nasty probem.
  786. * Several Makefile cleanups.
  787. Version 1.11.1 - Michael Bushnell, 1992-09.
  788. * Many bug fixes.
  789. Version 1.11 - Michael Bushnell, 1992-09.
  790. Version 1.10.16 - 1992-07.
  791. Version 1.10.15 - 1992-06.
  792. Version 1.10.14 - 1992-05.
  793. Version 1.10.13 - 1992-01.
  794. * Many bug fixes.
  795. * Now uses GNU standard configure, generated by Autoconf.
  796. * Long options now use `--'; use of `+' is deprecated and support
  797. for it will eventually be removed.
  798. * New option --null causes filenames read by -T to be
  799. null-terminated, and causes -C to be ignored.
  800. * New option --remove-files deletes files (but not directories)
  801. after they are added to the archive.
  802. * New option --ignore-failed-read prevents read-errors from affecting
  803. the exit status.
  804. * New option --checkpoint prints occasional messages as the tape
  805. is being read or written.
  806. * New option --show-omitted-dirs prints the names of directories
  807. omitted from the archive.
  808. * Some tape drives which use a non-standard method of indicating
  809. end-of-tape now work correctly with multi-tape archives.
  810. * --volno-file: Read the volume number used in prompting the user
  811. (but not in recording volume ID's on the archive) from a file.
  812. * When using --multi-volume, you can now give multiple -f arguments;
  813. the various tape drives will get used in sequence and then wrap
  814. around to the beginning.
  815. * Remote archive names no longer have to be in /dev: any file with a
  816. `:' is interpreted as remote. If new option --force-local is given,
  817. then even archive files with a `:' are considered local.
  818. * New option --atime-preserve restores (if possible) atimes to
  819. their original values after dumping the file.
  820. * No longer does tar confusingly dump "." when you don't tell it
  821. what to dump.
  822. * When extracting directories, tar now correctly restores their
  823. modification and access times.
  824. * Longnames support is redone differently--long name info directly
  825. precedes the long-named file or link in the archive, so you no
  826. longer have to wait for the extract to hit the end of the tape for
  827. long names to work.
  828. Version 1.10 - Michael Bushnell, 1991-07.
  829. * Filename to -G is optional. -C works right. Names +newer and
  830. +newer-mtime work right.
  831. * -g is now +incremental, -G is now +listed-incremental.
  832. * Sparse files now work correctly.
  833. * +volume is now called +label.
  834. * +exclude now takes a filename argument, and +exclude-from does
  835. what +exclude used to do.
  836. * Exit status is now correct.
  837. * +totals keeps track of total I/O and prints it when tar exits.
  838. * When using +label with +extract, the label is now a regexp.
  839. * New option +tape-length (-L) does multi-volume handling like BSD
  840. dump: you tell tar how big the tape is and it will prompt at that
  841. point instead of waiting for a write error.
  842. * New backup scripts level-0 and level-1 which might be useful
  843. to people. They use a file "backup-specs" for information, and
  844. shouldn't need local modification. These are what we use to do
  845. all our backups at the FSF.
  846. Version 1.09 - Jay Fenlason, 1990-10.
  847. Version 1.08 - Jay Fenlason, 1990-01.
  848. Versions 1.07 back to 1.00 by Jay Fenlason.
  849. * See ChangeLog for more details.
  850. Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2003,
  851. 2004, 2005, 2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc.
  852. This file is part of GNU tar.
  853. GNU tar is free software; you can redistribute it and/or modify
  854. it under the terms of the GNU General Public License as published by
  855. the Free Software Foundation; either version 3, or (at your option)
  856. any later version.
  857. GNU tar is distributed in the hope that it will be useful,
  858. but WITHOUT ANY WARRANTY; without even the implied warranty of
  859. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  860. GNU General Public License for more details.
  861. You should have received a copy of the GNU General Public License
  862. along with tar; see the file COPYING. If not, write to
  863. the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
  864. Boston, MA 02110-1301, USA.
  865. Local variables:
  866. mode: outline
  867. paragraph-separate: "[ ]*$"
  868. eval: (add-hook 'write-file-hooks 'time-stamp)
  869. time-stamp-start: "changes. "
  870. time-stamp-format: "%:y-%02m-%02d"
  871. time-stamp-end: "\n"
  872. end: