[GuB-42]

Why does it needs a new name?

I had a good idea of what it did before reading the article, it is a long name but not Java-long, and none of the suggestions so far are clear to me, even after reading the article.

The only somewhat confusing part is the "twice", because it can be more than twice. But if you think about it, if it has been changed more than twice, it had to be changed twice at some point, so it is not totally wrong.

[mjd]

At the time I started writing the article, the utility was called `analyze-commits`. Hard to think of a worse name than that!

By the time I finished writing it I had come up with a less crappy name, but I thought I'd leave the question in the post anyway.

[antonvs]

If you’re looking for something descriptive and not clever/catchy, I propose ‘find-repeat-changes’.

[0manrho]

Just gonna +1 this. It's still fairly short, descriptive and to the point, which I generally prefer to something more "trendy" or "clever". I like it.

[1718627440]

What about git n-changed or even git nchanged. I feel like these commands need to be short and not consist of >3 words.

[alex-moon]

Or indeed "Find Repeat EDits" or fred for short.