Fix NEWS
This commit is contained in:
18
NEWS
18
NEWS
@@ -16,12 +16,20 @@ it is treated as tar command line option.
|
||||
|
||||
Use the --verbatim-files-from option to disable this special handling.
|
||||
This facilitates the use of tar with file lists created automatically
|
||||
(e.g. by file(1) command).
|
||||
(e.g. by find(1) command).
|
||||
|
||||
This option affects all --files-from options that occur after it in
|
||||
the command line. Its effect is reverted by the
|
||||
--no-verbatim-files-from option.
|
||||
|
||||
* --null option reads file names verbatim
|
||||
|
||||
The --null option implies --verbatim-files-from. I.e. each line
|
||||
read from null-delimited file lists is treated as a file name.
|
||||
|
||||
This restores the documented behavior, which was broken in version
|
||||
1.27.
|
||||
|
||||
* New options: --owner-map=FILE and --group-map=FILE
|
||||
|
||||
These two options provide fine-grained control over what user/group
|
||||
@@ -40,14 +48,6 @@ NEWID is supplied, NEWNAME must also be either a valid name or a
|
||||
+ID. Otherwise, both NEWNAME and NEWID need not be listed in the
|
||||
system user database.
|
||||
|
||||
* --null option reads file names verbatim
|
||||
|
||||
The --null option implies --verbatim-files-from. I.e. each line
|
||||
read from null-delimited file lists is treated as a file name.
|
||||
|
||||
This restores the documented behavior, which was broken in version
|
||||
1.27.
|
||||
|
||||
* Sparse file detection
|
||||
|
||||
Tar now uses SEEK_DATA/SEEK_HOLE on systems that support it. This
|
||||
|
||||
Reference in New Issue
Block a user