mirror of https://github.com/digint/btrbk
btrbk: default timestamp_format=long
This is a relict of early days of btrbk, and I have already hesitated for too long to change the default from legacy "short" to sane "long" format. Tests show that the scheduling behaves in a sane/expected way if this change is applied unattended. I suppose everybody who has preserve_hour_of_day set is already using timestamp_format=long.pull/446/head
parent
c5273a8745
commit
8cc74fecc1
2
btrbk
2
btrbk
|
@ -81,7 +81,7 @@ my %config_options = (
|
|||
# NOTE: the parser always maps "no" to undef
|
||||
# NOTE: keys "volume", "subvolume" and "target" are hardcoded
|
||||
# NOTE: files "." and "no" map to <undef>
|
||||
timestamp_format => { default => "short", accept => [ "short", "long", "long-iso" ], context => [ "global", "volume", "subvolume" ] },
|
||||
timestamp_format => { default => "long", accept => [ "short", "long", "long-iso" ], context => [ "global", "volume", "subvolume" ] },
|
||||
snapshot_dir => { default => undef, accept_file => { relative => 1, absolute => 1 }, context => [ "global", "volume", "subvolume" ] },
|
||||
snapshot_name => { c_default => 1, accept_file => { name_only => 1 }, context => [ "subvolume" ], deny_glob_context => 1 }, # NOTE: defaults to the subvolume name (hardcoded)
|
||||
snapshot_create => { default => "always", accept => [ "no", "always", "ondemand", "onchange" ], context => [ "global", "volume", "subvolume" ] },
|
||||
|
|
|
@ -96,7 +96,7 @@ otherwise.
|
|||
|
||||
*timestamp_format* short|long|long-iso::
|
||||
Timestamp format used as postfix for new snapshot subvolume
|
||||
names. Defaults to ``short''.
|
||||
names. Defaults to ``long''.
|
||||
+
|
||||
--
|
||||
ifndef::backend-docbook,backend-manpage[]
|
||||
|
|
Loading…
Reference in New Issue