[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: Bob Proulx <bob_at_proulx.com>
Date: 2006-08-27 18:56:07 CEST

Christopher Taylor wrote:
> Stupid question time on this ... why can't you just assign each
> developer a branch to work on and then merge their branches back into
> the repository after it has been reviewed?

It is a good question. But the answer is that even in a branch what
the developer has checked in is still checked into the subversion
repository and is still stored in the back end. Using a branch will
not prevent license violations from occurring and will not prevent the
back end store from running out of disk space for everybody because a
(bad) developer committed things that they should not have committed.
The subversion repository still has everything in it. It is just less

To make an analogy, this would be like renaming files so that they are
"hidden files" and not shown in a typical directory listing. You
won't see them in typical use after that but the files will still be
there just the same.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 27 18:57:25 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.