Matthew Berney wrote:
> There are many ways that this can be achieved with CVS. One of the
> administrative files "commitinfo" allows you to execute a script when the
> commit operation occurs. This is a "pre-commit" trigger. You could
> implement some sort of function to validate the files prior to checkin.
Yes, but that is automatic. Script cannot determine if the code is right or
if the code is wrong.
>
>
> Another approach is to checkin on a branch and then merge the branch onto
> the main. If the merge and validation test is successful, then commit to
> the main. Otherwise, reject the merge request.
>
> Matt
>
It means I must create separate branches for all developers ?
thanks
Łukasz Michalski
