Preventing bad commits

Some of our developers are unclear on the concept of version control,
and tend to upload a lot of junk in the system -- entire directories of
third-party code, for example, that they wanted to show other people.

How can I set things up so I can review developer commits, and back out
any mistakes?

What I need is some kind of workflow system, akin to the ones found in
content management systems, that allow a manager to review changes
before documents get posted to the next level.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 10 22:44:32 2006