Is “inconclusive change” a generic term in version control?

Question

Continuous change is a term used to describe minor contributions that are supposed to break nothing and shrink like NBC. A typical example: formatting the source file or adding a comment - this really, really should not break the assembly (of course, there are always exceptional cases).

Is this a common term in version control negotiations? I especially ask those who are familiar with RC systems. I sometimes use "NBC", but I never heard anyone else use it, so I thought ...

(btw: don't trust wikipedia as a source)

To explain a little why I find this term useful:

Help Avoid Finding the Wrong Place
Using an autoformatter usually results in a lot of changed strings, which makes the difference between versions useless. The “NBC” in the change list is a hint that there is no need to look at the difference of changes when looking for changes that have broken something.

Answer 1

I was in the SCM space for some time and never heard or used this term in relation to version control of source files or changes, such as comments / formatting, that did not change the output of the assembly.

, (, ) .

Answer 2

API . , - , , "" - .

, , RCS. diff , . , diff, , diff .

, ? ? , , ", , "?

Answer 3

The "security feature" is sometimes used in fBSD for commits made shortly before code freezes.