-
-
Notifications
You must be signed in to change notification settings - Fork 661
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exa is unmaintained, please use the active fork eza instead #1243
Comments
Second occurrence of |
Thank you so much for keeping us updated on the situation. I'm sure we all appreciate your effort to keep this project going! <3 |
Thanks, fixed the typo x) |
exa is unmaintained. Ref: ogham/exa#1243
exa is unmaintained, eza is a maintained fork. See ogham/exa#1243. Signed-off-by: Christopher Larson <kergoth@gmail.com>
You can archive this repository, to mark it as unmaintained. People then cannot submit PRs and there is a big warning that this is archived. IMHO this would make it more obvious this is not maintained anymore. Edit: Oh sorry just read your OP, forget it, you said that there already. Anyway, thanks for maintaining it so long! 🤗 |
ogham/exa#1243 among other things
exa is no longer maintained. eza is a new community-based fork that continues that work. ogham/exa#1243
exa is unmaintained. See ogham/exa#1243
|
`exa` is unmaintained: ogham/exa#1243 Switch to the recommended community fork (which seems to have critical mass activity).
Using eza instead of exa ogham/exa#1243
Just found this issue when today, Thursday, July 25, 2024, for the first time brew let me know that @ariasuni , thanks for all your work keeping exa going, and for taking the time to help people find |
Use eza-community/eza instead. ogham/exa#1243
According to [this][issue], `exa` is now unmaintained. It recommends to use the actively maintained [`eza`][eza] fork instead. [issue]: ogham/exa#1243 [eza]: https://github.com/eza-community/eza
eza is an active fork of exa, which is now unmaintained. See ogham/exa#1243
eza is an active fork of exa, which is now unmaintained. See ogham/exa#1243
What happend to him @ogham? |
No idea, I didn’t hear from him since 2021-04-03, but his website is still up. Last activity from his part I can find online is a retweet on twitter dot com of a post from 2022-07-06. |
Last I activity I was able to find is 12th June 2023 and 9th June 2023 https://git.sr.ht/~ogham/bugbear-go/commit/e9375fd8bdba2627ec400b2ec6869186a5bca1ad Website's certificate was issued Wednesday, August 14, 2024 at 1:54:55 PM although probably been done automatically by certbot. |
exa is unmaintained, please use the active fork eza instead.
A lot of work has already been put into it by other people, and I’ll be porting my ongoing work to this fork. Sadly, @ogham seems unreachable so I can’t really archive the project… for now, I’ll redirect people to eza, from the README and issues page.
A page is turning for me: it was great maintaining exa on my own for a while but it wasn’t sustainable and I was in burnout, I’m so glad people finally created a fork that I could contribute to instead of having to handle the whole thing.
The text was updated successfully, but these errors were encountered: