RE: Re: commit-policy

There is simple sollution for managing branches: svnmerge.
It resolve many problems in merge tracking.

> -----Original Message-----
> From: treuthmemocomp.de [mailto:treuthmemocomp.de]
> Sent: Friday, March 07, 2008 1:13 PM
> To: devscarab.tigris.org
> Subject: Re: commit-policy
> 
> Hi all,
> 
> I was wondering if using a branch for every new
commiter would give
> somebody a hard time to keep all that branches in sync
with the trunk?
> Shouldn't the changes in the trunk be merged back into
the several
> branches to prevent something sneaking back into the
trunk from an
> outdated branch?
> Or am I overlooking something here?
> 
> Regards,
> Torsten
> 
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribescarab.tigris.org
> For additional commands, e-mail: dev-helpscarab.tigris.org


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribescarab.tigris.org
For additional commands, e-mail: dev-helpscarab.tigris.org