News for hackers. Stuff that matters.

A comment on Neovim. Parent comment

Re:Neovim by tarruda on Friday February 21, 2014 @02:03PM (#7278707)
As the author I would like to contribute changes back, search vim_dev mailing list for 'message loop' and 'job control' and you will find two patches I've sent that werent even commented by Bram.

This fork changes so much that its impossible that it will ever be accepted

[ Parent | on HN ]
Re:Neovim by bronson on Friday February 21, 2014 @07:56PM (#7280493)
I TOTALLY hear that.

Maybe an GCC/EGCS, eglibc/glibc, or (as nfm points out) Yarv/MRI scenario could work. First prove your mettle (will take donkey's years), then upstream can jump to your stable code base in one glorious commit.

Hope you can mention in the readme that upstreaming is not a goal... It might be hard to get the wording right but it would have made my first impression quite a bit less skeptical. :)

[ Parent | on HN ]
Re:Neovim by nfm on Friday February 21, 2014 @04:53PM (#7279684)
Maybe we can hope for an MRI/YARV scenario!
[ Parent | on HN ]