krino.git/internal/dup, 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:47:35Za content class is worked out once, not once per copy2026-09-17T11:47:35ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T11:47:35Zurn:sha1:b596085d2391ce3701fa6820a6728ba634ac453b
Lookup walked the whole size group for every file in it, so N copies of
one file cost N walks of an N-member group, each taking the index's
lock at every step - which is why more workers made it slower rather
than faster. Every member of a class elects the same original (the
invariant identicalTo already documents and a test already pins), so
the class is memoised on the first walk and every later member is a
map lookup.
Measured over identical files, invented data, same machine:
500 files 0.17s -> 0.12s
2000 files 1.89s -> 0.58s
and the plans are byte-identical once the sandbox path is normalised.
The test counts walks: one per content class, not one per file.
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.
comments that explain the code, not how it was written2026-09-17T10:11:42ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T10:11:42Zurn:sha1:bddbd74e4a73e8e32bcf648efd1cac5655f6d0cd
About 340 comments cited the development process: task and plan
numbers, fix waves, rulings, reviewers, and the author in the third
person with a date. None of that exists outside the work itself, so to
a reader it pointed at nothing. Each one now states the engineering
reason it was standing in front of; where a comment was provenance and
nothing else, it is gone.
References to docs/design.md and docs/gui-design.md by section stay:
both ship with the repository. The design documents lose their
amendment diaries - CHANGELOG.md is that record - and the GUI's says
plainly that the window has gone further than the document.
Only comments changed. Every .go file was parsed and its code printed
with comments stripped, before and after: the two hashes are identical
across all 175 files.
duplicate warnings share one format2026-09-14T21:48:23ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:48:23Zurn:sha1:1bb5097986558ee7dd3aeaf8e7defefdf91ae4b6krino: release 0.0.1 — man pages, install, examples, cross and release, README, changelog2026-09-13T00:31:32ZLukasz Kasprzaklukas@labunix.xyz2026-09-13T00:31:32Zurn:sha1:26c94eb3db62ec6eebbf8d22c11afe691d9520c4
Also: undo removes the directories its run created; a hardlink is never a
duplicate of its own other name; a flag written before "undo" is honoured;
--version prints no leading v. Duplicate conditions with different scopes
not sharing an original is documented as a known limitation.
krino: planning — chains, placeholders, conflicts, JSON2026-09-12T10:58:14ZLukasz Kasprzaklukas@labunix.xyz2026-09-12T10:58:14Zurn:sha1:24a84671ace373ae331fa83a1ff484990f4dff0ekrino: matching — scan, ignore, conditions, extraction, duplicates, explain, dry run2026-09-11T23:22:12ZLukasz Kasprzaklukas@labunix.xyz2026-09-11T23:22:12Zurn:sha1:3b36a48b7ce5a53a9366f3b31f94311f178e2553