Here is an example from only a few days ago of many chopped off move summaries (it is from my contributions listing, so anyone viewing it would already know the user performing the action), which would be alleviated by removing the redundant information from the edit summary. I realise that this has been discussed before but I'm bringing it up again because it's something that has frustrated me for over five years now and, having apparently made over 10,000 moves on enwiki, it is an issue that causes me irritation almost daily in my regular editing/administrating.

Here's an example. This is what immediately appears after clicking "show mergeable edits". If I click "merge revisions" now (even in this very basic example where there is only one possible revision that could be merged), it will not do anything. I have to first tick the box next to the revision in question, which strikes me as the opposite of what the default should be.

Hi @Sethakill. I just used this tool for the first time since your change here went live. I'm not sure exactly how to word this, but is there any chance that we could go back to if no revision/button is selected and I hit "merge revisions" it just merges all the revisions? This is I think how it used to be and also how it works for undeletions (i.e. it's assumed you want all of it unless you specify otherwise).

@matmarex Sorry to be a pain, but any chance of a status/progress update for this? I tried reading the gerrit but was a bit confused to say the least. Really appreciate the work you've done on this so far.

Thanks to those who have pointed me here after my inquiries at the en.wp's village pump. I see this is currently unassigned, does anyone know any devs who might be interested in this that I could try to prod into working on it?

Just noting for the record as this seems to have been brought up recently (progress?): please don't remove the "move associated talk page" tickbox. There is a lot of time during my admin work where I want to leave it unticked, especially during histmerges.

I'm using Firefox 41.0 on Mac OSX Yosemite. Thanks for the quick response.

If there is a bug with this change do I add it here or open a new task? Hopefully someone who is subscribed to this gets it to the right place.

@Aklapper Thanks for the response. You've basically answered my first question, which was going to be "is anything going to happen with this bug, because I'd absolutely love it if someone could fix it?" Judging by your response I guess the answer is "not in the near future, at least". My next question would be "is there some way I can convince a developer to work on this bug?" I am happy to offer a bribe :)

Many thanks for this. It's made cleaning up after moves a lot easier.

Err, 'bump'? Not really sure how Phabricator works, but this is still a bug and the problem is still the same as was described in 07 (if I'm reading things correctly).