[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Preventing bad commits

From: Peter Werner <l.svn_at_vasas.no-ip.org>
Date: 2006-08-21 10:51:10 CEST

> > 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.
> I feel your pain. I don't know why this is such a hard concept for
> many people to understand.
> > How can I set things up so I can review developer commits, and back out
> > any mistakes?

Perhaps two repositories? You "forward" good commits. This way you
will have a clean repository. The harder part is how to organize
cleaning out the developers' repo. You can overwrite it and they need
to do a new checkout. (Take care about changed revision numbers!)


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 21 10:52:47 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.