2026-10-15 - 2026-10-22
Overview
1 Release published by 1 user
Published
v0.0.2
12 Pull requests merged by 1 user
Merged
#110 next into main
Merged
#131 Keep modules, lint cache and system packages in check builds (closes #109)
Merged
#130 Install from @latest, retract v0.0.1, print a go-installed binary's version (closes #116)
Merged
#129 scan: create the database's directory where its path leads (closes #119)
Merged
#128 scan: never record its own database files (closes #115)
Merged
#127 scan: skip OS default excludes, and record nothing on filesystems that are not persistent (closes #124)
Merged
#126 Show the progress rate over the last 5 seconds, and where a phase waits after 10 seconds with no item done (closes #125)
Merged
#123 Add sfdupes info: show the database's details (closes #117)
Merged
#122 report: show its phases as N of M, with progress, elapsed time and ETA (closes #114)
Merged
#121 trees: show its phases as N of M, with progress, elapsed time and ETA (closes #113)
Merged
#120 scan: show each phase as N of M, with progress, elapsed time and ETA, also while it waits (closes #112)
Merged
#118 Name the database each command uses on stderr (closes #111)
11 Issues closed from 1 user
Closed
#109 make test goes over 60 seconds when the kept Go build cache has been removed
Closed
#116 go install @latest must install main's tip; retract v0.0.1; a go-installed binary must say which version it is
Closed
#119 scan creates the database's folder in the wrong place when the path holds .. after a symlink
Closed
#115 scan records its own database files when the database is inside a scanned operand
Closed
#124 scan skips OS-appropriate default excludes (/proc, /sys, /tmp, /run, /var/tmp on Linux)
Closed
#125 scan prints nothing for long stretches and looks frozen, then reports over 1,000 files a second
Closed
#117 Add sfdupes info: show the database's details
Closed
#114 report: never sit silent; show its phases as N of M with progress, elapsed time and ETA
Closed
#113 trees: never sit silent; show its phases as N of M with progress, elapsed time and ETA
Closed
#112 scan: show each phase as N of M, with progress, elapsed time and ETA, also while it waits
Closed
#111 Say which database file each command uses, and document when scan writes to it
14 Issues created by 2 users
Opened
#111 Say which database file each command uses, and document when scan writes to it
Opened
#112 scan: show each phase as N of M, with progress, elapsed time and ETA, also while it waits
Opened
#113 trees: never sit silent; show its phases as N of M with progress, elapsed time and ETA
Opened
#114 report: never sit silent; show its phases as N of M with progress, elapsed time and ETA
Opened
#115 scan records its own database files when the database is inside a scanned operand
Opened
#116 go install @latest must install main's tip; retract v0.0.1; a go-installed binary must say which version it is
Opened
#117 Add sfdupes info: show the database's details
Opened
#119 scan creates the database's folder in the wrong place when the path holds .. after a symlink
Opened
#124 scan skips OS-appropriate default excludes (/proc, /sys, /tmp, /run, /var/tmp on Linux)
Opened
#125 scan prints nothing for long stretches and looks frozen, then reports over 1,000 files a second
Opened
#132 the algorithm in "Duplicate detection" is nonsensical
Opened
#133 display issues
Opened
#134 hash storage efficiency
Opened
#135 Rewrite README.md and the other prose documents sentence by sentence, on Fable
2 Unresolved Conversations
Open
#56
Trial run at real scale on the target server before tagging 1.0.0
Open
#98
Finish 1.0 and tag it; after that, bugfixes only