When merging terms, do not create a revision.

Problem/Motivation

I just did a long series of term merges, merging approx 10 terms, in to 10 other terms..., in individual steps on an ~30,000 node sized website.

The node_revisions__body table went from a few hundred MB, up to 4GB...

Can this module be given a feature to NOT create a revision if desired? Just altering the existing one?

Each term merge step, created a new revision. Meaning every node that was impacted was given 10 revisions...

This will help keep the DB size in control when a revision isn't needed.

In this business use case, we were cleaning up bad terms that were wrongly created, not doing content edits that might need to be rolled back. (In fact, I'm not sure we could roll back, since the terms are destroyed? I've never tested that scenario)