[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: Jamie Wellnitz <Jamie.Wellnitz_at_emulex.com>
Date: 2006-08-10 22:47:19 CEST

On Thu, Aug 10, 2006 at 03:42:55PM -0500, Chris wrote:
> 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.

2 general methods:

You could have developers check into a staging branch, and then merge
changes from there to the production branch (or trunk).

You could also require some review process before checkin.

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>

Regards,
        Jamie

---------------------------------------------------------------------
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:48:40 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.