-
Notifications
You must be signed in to change notification settings - Fork 33
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 Emacs's master branch #49
Comments
@monnier, if you already did that merge work, is there any chance to transmogrify the changes into here as a github pull request? |
I'd much rather that people help us maintain the version that's bundled with Emacs, so all users benefit. BTW, that version could trivially be distributed via GNU ELPA if the issue is that you want users of older Emacsen to benefit as well. |
Sorry that I haven't looked at this repository for a long time. I like the idea of making the Emacs core the authoritative source. I think the best situation would be to archive this repository and link to Emacs itself. I will wait for an ack from @renormalist first; he has done all the maintenance work so can make the final decision. |
@jrockway - I am totally fine to use a more official place, and to contribute to @monnier 's repository. It is very ok for me to "close" this repository here into some "readonly" mode for archive purposes, or whatever. I also haven't actively maintained my version branches for modern perl or perl6 syntax. @monnier - Strange that I didn't understand that situation when you first created this ticket here in 2018 and I asked you for a pull request into here. You are totally right in your answer. |
I've merged the changes from this repository's master branch into Emacs's master branch. And I also installed various other cleanups into Emacs's master branch (e.g. to use lexical-binding and solve the many resulting warnings).
The text was updated successfully, but these errors were encountered: