Or the opposite: after 15+ years with one tool, you'll master it to a level that is very hard to give up. All the annoyances by now have workarounds, all the problems are accounted for, all the monitoring and hardening is in place (and for openbsd in particular: all the code has been audited and reviewed several times). Why lose all that in name of some abstract productivity gain that will likely be offset by years of pain getting up to speed with the new tool?
Would signed commits be a value add over CVS? You'd think the security conscious OpenBSD ecosystem would value a way to verify the integrity of the source tree for any given commit or tag or release. I have to admit I'm not an OpenBSD user so I have no idea if they have something similar for CVS these days?
