libburnia/libisoburn
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

New -compliance rules rrip_tf_long and rrip_tf_short

Browse Source
This commit is contained in:
Thomas Schmitt
2025-06-24 19:10:24 +02:00
parent 86a7a587eb
commit 433d4be78a
5 changed files with 131 additions and 94 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
xorriso/xorriso.1
View File

@ -9,7 +9,7 @@
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH XORRISO 1 "Version 1.5.7, Jun 10, 2025"
.TH XORRISO 1 "Version 1.5.7, Jun 17, 2025"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -3258,6 +3258,17 @@ Both words then stem from a reserved subset of UCS\-2.
.br
"always_gmt" stores timestamps in GMT representation with timezone 0.
.br
"rrip_tf_long" forces use of the long form of RockRidge timestamps.
This form is not understood by Linux kernels older than 6.16.
.br
"rrip_tf_short" is the default. It enables use of the short form of RockRidge
timestamps, which cannot express times after end of year 2155 but is understood
by a wide range of operating systems.
The short form is then used with all files or directories which have atime,
ctime, and mtime before 01 Jan 2150 UTC. (The six years up to 2156 may serve
as last opportunity to enhance readers after libisofs was changed to continue
using the short form.)
.br
"rec_mtime" records with non\-RockRidge directory entries the disk file's
mtime and not the creation time of the image. This applies to the ECMA\-119
tree (plain ISO 9660), to the Joliet tree, and to the tree of an Enhanced