rules to exclude file segments from change detection
We have a lot of automatic generated files which are under version control.
These files often contain a timestamp of their creation and some other information which aren't that much important and don't need to be controled by plastic.
The idea: It would be nice if I could define a rule (maybe using a regex) to define lines or segments in these files which maybe change but don't cause plastic to show them as pending changes.
We have something called the hidden changes list. Why don’t you check it?
-
Anonymous commented
It sounds to me like this is based on a wrong usage. Generated text/code should be separated from the rest (in a different file), preferably not added to the source control at all.
There should be a very good reason why not doing this, having problems with the source control is just one problem of this usage.