It's not a replacement for the maintainer, it's a replacement for your vcs's 'commit' command.
No vcs that I'm familiar with has a commit command that will stop you from merging silly code
to trunk either.
Posted Aug 1, 2008 6:08 UTC (Fri) by dlang (✭ supporter ✭, #313)
[Link]
with all the good choices of VCS out there, why would you choose to use one that required a
replacement for it's commit command instead of just using one that doesn't require such a
replacment?
OLS: Shuttleworth on free software development
Posted Aug 1, 2008 6:27 UTC (Fri) by njs (subscriber, #40338)
[Link]
Because none of those VCSes have the functionality you want, i.e., to aid the desired workflow
of all development on branches, clean merges to trunk, trunk always passes testsuite...?