4 ms·
Well, if there are enough people working on a repository, you might be inundated with changes every time you update. You'd never suspect anything unless you kne
by lutorm 17y ago
Well, if there are enough people working on a repository, you might be inundated with changes every time you update. You'd never suspect anything unless you knew which files specific users should be editing, and checking that for each patch would probably be prohibitively time consuming.
But unless perforce allows you to delete history, it shouldn't be a big deal to fix. The hard part is finding it.
I wonder if there are automated systems that can check the patches users commit and look for "outliers" in content or style?
- fierarul 17y agoSo I guess Google's style of code-reviewing every commit should keep them safe from this...
- kvs 17y agoGood point; This is something I wanted to see discussed but the paper didn't touch on it at all. It just focused on tools and vulnerabilities in the tool and didn't dip into the process surrounding the tool.