Stamp It! All Programs Must Report Their Version(michael.stapelberg.ch)
michael.stapelberg.ch
Stamp It! All Programs Must Report Their Version
https://michael.stapelberg.ch/posts/2026-04-05-stamp-it-all-programs-must-report-their-version/
9 コメント
> --moreversion
Suggestion: more conventional and intuitive would be: --version --verbose
Suggestion: more conventional and intuitive would be: --version --verbose
I took it to be more like "The answer? Use --version. And if that don't work, use --moreversion."
https://www.youtube.com/watch?v=SNgNBsCI4EA
https://www.youtube.com/watch?v=SNgNBsCI4EA
This is not really a huge issue.
Most commercial software gives you a detailed version report.
Either way, the simplest solution would be -v, and -vv and -vvv … don’t do moreversion or lessversion.
The equivalent would be —version —version —version.
Most commercial software gives you a detailed version report.
Either way, the simplest solution would be -v, and -vv and -vvv … don’t do moreversion or lessversion.
The equivalent would be —version —version —version.
The version seems to be the number one information in order to avoid making things worse! Not all solutions apply to all versions of a running product.
Great post! I propose all programs have a `--version` flag. Anything similar for Rust + Cargo right now?
I meant `--stamp` lol
Dang please mark this post for boosting?
2.4.16-12 vs 2.4.16-35 - obviously -35 is later.
But 2.4.16-bcbd1c6 vs 2.4.16-d645104 - which is later? Compile dates won't necessarily help because "earlier" code could have been compiled later.
It's forcing the versioning to do something it shouldn't, arguably, but is nice to have something that the user can decipher (even if you still should have the commit).