New -compliance rules rrip_tf_year0 and rrip_tf_1900
This commit is contained in:
@@ -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 17, 2025"
|
||||
.TH XORRISO 1 "Version 1.5.7, Sep 15, 2025"
|
||||
.\" Please adjust this date whenever revising the manpage.
|
||||
.\"
|
||||
.\" Some roff macros, for reference:
|
||||
@@ -3269,6 +3269,13 @@ 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
|
||||
"rrip_tf_year0" enables writing of RockRidge timestamps before year 1900 AD
|
||||
down to year 0 (= 1 BC).
|
||||
.br
|
||||
"rrip_tf_1900" is the default. It restricts timestamps to at least
|
||||
Jan 1 1900 UTC because the Linux kernel up to at least version 6.16
|
||||
misrepresents times before year 1900 as Jan 1 1970 00:00:00 UTC.
|
||||
.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
|
||||
|
Reference in New Issue
Block a user