Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-09-28 | 0.34.00.34.0 | Junegunn Choi | |
2022-08-29 | 0.33.00.33.0 | Junegunn Choi | |
2022-08-02 | 0.32.00.32.0 | Junegunn Choi | |
2022-07-21 | 0.31.0 | Junegunn Choi | |
2022-04-04 | 0.30.00.30.0 | Junegunn Choi | |
2021-12-25 | 0.29.00.29.0 | Junegunn Choi | |
2021-11-04 | 0.28.00.28.0 | Junegunn Choi | |
2021-04-06 | 0.27.00.27.0 | Junegunn Choi | |
2021-03-13 | 0.26.00.26.0 | Junegunn Choi | |
2021-01-08 | Update default number version (#2307) | calvin ardi | |
2020-10-29 | Assign default number version (without patch version) | Junegunn Choi | |
So that you can still build and use fzf even when the precise version number is not injected via -ldflags. | |||
2020-10-28 | Panic when fzf was built without version information0.24.0-1 | Junegunn Choi | |
So that the package maintainers would immediately know that the build is incorrect. But is there a way to make build simply fail? Related: https://github.com/junegunn/fzf.vim/issues/1150 | |||
2020-10-27 | 0.24.0-rc10.24.0-rc1 | Junegunn Choi | |
2020-01-19 | Add pledge(2) support (OpenBSD only) via a 'protector' package. (#1297) | Aaron Bieber | |
2017-06-02 | Add git revision to --version output | Junegunn Choi | |
2017-06-02 | Restructuring: main package in project root | Junegunn Choi | |