ncdu 1.14.2
This commit is contained in:
parent
2042aa6ca1
commit
442da67055
23 changed files with 109 additions and 8 deletions
|
|
@ -28,8 +28,8 @@ additions to the existing format.
|
|||
|
||||
## Metadata
|
||||
|
||||
The `<metadata>` element is a JSON object holding whatever (short)
|
||||
metadata you'd want. This block is currently (1.9-1.13) ignored by ncdu when
|
||||
The `<metadata>` element is a JSON object holding whatever (short) metadata
|
||||
you'd want. This block is currently (1.9-1.14.2) ignored by ncdu when
|
||||
importing, but it writes out the following keys when exporting:
|
||||
|
||||
progname
|
||||
|
|
@ -95,7 +95,7 @@ ino
|
|||
: Number. Inode number as reported by `lstat().st_ino`. Together with the Device
|
||||
ID this uniquely identifies a file in this dump. In the case of hard links, two
|
||||
objects may appear with the same (`dev`,`ino`) combination. A value of 0 is
|
||||
assumed if this field is absent. This is currently (ncdu 1.9-1.13) not a
|
||||
assumed if this field is absent. This is currently (ncdu 1.9-1.14.2) not a
|
||||
problem as long as the `hlnkc` field is false, otherwise it will consider
|
||||
everything with the same `dev` and empty `ino` values as a single hardlinked
|
||||
file. Accepted values are in the range of `0 <= ino < 2^64`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue