On Mon, 04 Dec 2000, [EMAIL PROTECTED] wrote:
> Hi all
>
> I am new to CVS and CM but am responsible now for managing a small
> repository in my company.I have no one experienced in this field to
> ask these questions. I have a question in general about
> configuration management.Is it necessary to document check outs from
> a CVS repository?Will it serve any purpose? will it make keeping
> track of releases,tags,branches etc more easy?is it a good practice
> to allow uncontrolled check ins to all developers in a project?If
> someone can advice on this ,I will be grateful.
I think it's interesting to have control over what people can
checkout. Running some kind of checkout trigger would be interesting
and would allow one to have more control than by simply using Unic
permissions.
For the quick look I had at Cederqvist, there's no such an option but
you can get something similar to that with 'cvs edit'.
I think that having a kind of 'checkoutinfo' file is interesting.
See you,
--
Godoy. <[EMAIL PROTECTED]>
Departamento de Publica��es Conectiva S.A.
Publishing Department Conectiva Inc.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
