-
Notifications
You must be signed in to change notification settings - Fork 0
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
Merge with upstream? #1
Comments
Thanks, I am aware of that. In fact, this is the main reason why I paused this project. With the long frozen upstream thawed, I no longer feel the need to work on a fork. The original author would be in a better place maintaining it. Since there is quite some changes underlying, I do not really think it a good idea to contribute upstream. Will take a look if the bugs I discovered have been addressed by the upstream. |
For what it's worth, a GitHub fork might still have value if it makes submitting patches and bug reports easier. The original author's current model is to have people email him things privately, with him then addressing the emails about once a year. |
BTW, on the subject of "No further undo information", I filed this Emacs bug which might be related: |
Thanks for the suggestion, I didn't know that! Will take a look of the upstream changes after this project's fork point, and make a decision. I am no longer using undo-tree very often, so the chance of me continuing with this project is low. BTW, you might want to check out a totally different approach here. |
FYI, there has been some upstream activity since this project's fork point:
https://gitlab.com/tsc25/undo-tree/-/commits/master
The text was updated successfully, but these errors were encountered: