GP is correct, and this is quite normal: some people using Emacs master will not follow all the mailing list discussions and commits. So they will notice a change only after it is merged. Nothing wrong with this, and nothing wrong with being unhappy about such a change. What's wrong in my book is the nature of the reaction show in this article (see my comment in reply to @tarsius).
Some people only pick up releases, including test releases.
Some people only work with final releases.
All those people could find something suddenly not working well.
Those who are not sensitive changes just use whatever Ubuntu (or whatever) provides and are unconcerned with the development.
> Indeed, I only reimplemented the parts I saw as clearly beneficial. Most importantly, my patch improves stuff without breaking other stuff.
> Perhaps you can explain your use case for the rest of the changes, and if there's a good and compatible way to add them I'll be happy to look into it at some point.
> > - No filtering. > > - No navigation. > > - No default registers. > > - No possibility to configure a new command added to register.
> If you could elaborate about these bullets, and explain their use, that'd be great.
I think it's quite obvious that engaging further with someone who came in with this attitude after a review was finalized (after ~5-10 rounds of feedback, I should point ou) and a patch applied did not seem worth it.
into the master branch