From f2fc5f3389c1cc2f9d928bae5650911d42af8936 Mon Sep 17 00:00:00 2001 From: Marcus Holland-Moritz Date: Tue, 8 Apr 2025 13:11:41 +0200 Subject: [PATCH] docs(mkdwarfs): document `explicit` ordering --- doc/mkdwarfs.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/mkdwarfs.md b/doc/mkdwarfs.md index 57244cdf..29ff9752 100644 --- a/doc/mkdwarfs.md +++ b/doc/mkdwarfs.md @@ -289,7 +289,7 @@ Most other options are concerned with compression tuning: "normalize" the permissions across the file system; this is equivalent to using `--chmod=ug-st,=Xr`. -- `--order=`[*category*`::`]`none`|`path`|`revpath`|`similarity`|`nilsimsa`[`:`*opt*[`=`*value*][`:`...]]: +- `--order=`[*category*`::`]`none`|`path`|`revpath`|`similarity`|`nilsimsa`[`:`*opt*[`=`*value*][`:`...]]|`explicit:file=`*file*: The order in which inodes will be written to the file system. Choosing `none`, the inodes will be stored in the order in which they are discovered. With `path`, they will be sorted asciibetically by path name of the first file @@ -310,6 +310,9 @@ Most other options are concerned with compression tuning: Unlike the old implementation, `nilsimsa` ordering is now completely deterministic. See [Nilsimsa Ordering](#nilsimsa-ordering) for a detailed description of the algorithm. + `explicit` ordering allows you to specify a file that contains the paths in + the desired order. The paths must be relative to the `--input` path, but + may start with a leading `/`. - `--max-similarity-size=`*value*: Don't perform similarity ordering for fragments (or files if they are not split