krino.git/internal/engine/exclude_test.go, branch v0.0.12rule-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=v0.0.122026-09-17T10:54:06Zthe 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.
an undecided (stop) rule ends the search for that file2026-09-15T20:11:33ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T20:11:33Zurn:sha1:77a015b96db8727bb12d0869f180a44d087f6319a failed duplicate lookup is unknown, like unreadable content2026-09-15T20:10:44ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T20:10:44Zurn:sha1:6b38d302daa54140e4e26ad903297a1bba0cbd41docs: GUI design draft; code comments no longer name the owner2026-09-15T20:09:06ZLukasz Kasprzaklukas@labunix.xyz2026-09-15T20:09:06Zurn:sha1:bbc9b103acac96b83b150b81f2effe1b65c3f8a2(matched) is unknown after an undecided rule, so a catch-all leaves an unreadable file alone2026-09-14T22:32:11ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:32:11Zurn:sha1:ccd6faf3d10da0669631fb3e3ba17a46b9e63a09explain walks the directory for a duplicate test in an exclude too2026-09-14T22:27:43ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:27:43Zurn:sha1:59015f1f91d640502fdfc34019cf0154b5206bb8partial reads never cached; extractor version 3 discards 0.0.7 caches2026-09-14T22:27:13ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:27:13Zurn:sha1:fc6eda20555ea33f1a8260610056b7079c8e8fd9main excludes checked with the defaults' case and fold; Latin-1 decoding memory; hardlink election documented2026-09-14T21:53:54ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:53:54Zurn:sha1:0b155e8df3205aebf129091b517f4116665a5adcexplain: shows a duplicate's skipped delete, leaves the cache alone, walks only for duplicate tests2026-09-14T21:40:56ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:40:56Zurn:sha1:bb8b547023b0867f31d7452faceef5769a45b94b