reftable: document an alternate cleanup method on Windows
The new method uses the update_index counter, which isn't susceptible to clock inaccuracies. Signed-off-by: Han-Wen Nienhuys <hanwen@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Han-Wen Nienhuys committed
Apr 12, 2021 at 19:12 UTC
61a7660516131de505cf9654079a7ab7d7be704a
1 file changed
+7
-2
Documentation/technical/reftable.txt
+7
-2
@@ -1011,8 +1011,13 @@ reftable stack, reload `tables.list`, and delete any tables no longer mentioned
1011
in `tables.list`.
1012
1013
Irregular program exit may still leave about unused files. In this case, a
1014
-cleanup operation can read `tables.list`, note its modification timestamp, and
1015
-delete any unreferenced `*.ref` files that are older.
1014
+cleanup operation should proceed as follows:
1015
+
1016
+* take a lock `tables.list.lock` to prevent concurrent modifications
1017
+* refresh the reftable stack, by reading `tables.list`
1018
+* for each `*.ref` file, remove it if
1019
+** it is not mentioned in `tables.list`, and
1020
+** its max update_index is not beyond the max update_index of the stack
1021
1022
1023
Alternatives considered