krino.git/internal/plan/conflict_test.go, branch mainrule-based file sorter in Go, shows the plan before touching anything, applies only the files you choose, and can undo any run, with s-expression rules and a GTK 4 windowhttps://git.labunix.xyz/krino.git/atom?h=main2026-09-17T11:50:01Zthe suffix search continues instead of starting again at _12026-09-17T11:50:01ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T11:50:01Zurn:sha1:78d8313791f05defc9e0a9f2bad8e9710f741a60
Every file renamed onto one name probed stem_1, stem_2, ... from the
beginning, so N files cost N^2/2 Exists calls - a test here counts 1890
of them for 60 files. The search now continues from the highest suffix
already tried for that stem.
Within one plan that is the same answer: the taken set only grows while
a plan is built and the disk is not being written to, so a suffix taken
once stays taken. Proved rather than argued - with same_1 and same_3
already on disk and same_2 free, both versions put a file in the gap,
and the two plans are byte-identical.
1500 files renamed to one name: 2.63s -> 0.05s
the module path is git.labunix.xyz/krino2026-09-17T10:54:06ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T10:54:06Zurn:sha1:1884d56b0d399e9cdb80016a9c166b0120989933
So that go install can find it. cgit serves no go-import meta tag, so
nginx answers a ?go-get=1 request for /NAME with one pointing at
https://git.labunix.xyz/NAME.git; the alternative was carrying a .git
suffix through every import line forever.
One sed over the imports, both go.mod files, and the dependency gate's
whitelist. Nothing else depends on the path. go install works from the
next tag, the first release whose go.mod carries it.
plan 9: overwrite never trashes a directory or another scanned file2026-09-14T19:27:22ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T19:27:22Zurn:sha1:aca389f0e63713b890214cad950ac3aee7e6aaf4krino: planning — chains, placeholders, conflicts, JSON2026-09-12T10:58:14ZLukasz Kasprzaklukas@labunix.xyz2026-09-12T10:58:14Zurn:sha1:24a84671ace373ae331fa83a1ff484990f4dff0e