Date: 03/20/01
- Next message: Michal ROMAN: "[phplib] Similar Library"
- Previous message: Kristian Koehntopp: "Re: [phplib] path in Template Constructor"
- In reply to: Chris Johnson: "[phplib] PHPLIB Release 7.2d plans"
- Next in thread: Maxim Derkachev: "Re: [phplib] PHPLIB Release 7.2d plans"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In netuse.lists.phplib you write:
>Kristian, do I need to worry about other people with CVS commit access?
>That is, would it be appropriate for you to supply me with a list of all
>the PHPLIB CVS commiters, or is there an alternative way to insure the
>integrity of the work we do on a 7.2d release?
The NetUSE CVS is a large repository with a single passwd file
(I didn't know better at that time) and I didn't keep the mail
addresses of all users in that file. Basically, if you have
access to a single module, you can commit to all module. This
will always generate a mail on the appropriate -dev-List, for
your modules on phplib-dev <email protected>
Subscribe to phplib-dev <email protected> (by sending mail to
phplib-dev-subscribe <email protected>) to monitor your CVS
modules.
In the past, repository integrity was never a problem even with
that setup - we are not sourceforge-sized, and CVS gives you
unlimited undo.
Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>
- Next message: Michal ROMAN: "[phplib] Similar Library"
- Previous message: Kristian Koehntopp: "Re: [phplib] path in Template Constructor"
- In reply to: Chris Johnson: "[phplib] PHPLIB Release 7.2d plans"
- Next in thread: Maxim Derkachev: "Re: [phplib] PHPLIB Release 7.2d plans"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

