-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Greg,
Is it reasonable to suggest that a addinfo trigger could be run as a
part of the 'cvs commit' command should the client not happen to connect
to the server for a 'cvs add' operation?
The idea would be that having simpler triggers for various kinds of
policy makes the administration of a repository easier.
In a similar manner a trigger for 'cvs rm' could be implemented to
impose policy.
The timing of WHEN those triggers get invoked is what seems to be the
sticking point for folks... Like Derek, I would not mind a hack to allow a
the users to perform a check that all is well... perhaps a 'cvs -n commit'
should run those validation checks?
I have no objections and would in fact LIKE to see disconnected
operations for 'cvs add' if possible. I also suspect that changes to the
'cvs import' mechanism would aslo be useful.
For that matter, I would like to see disconnected 'cvs diff' commands
where possible for users that already have a CVS/Base/* version of the
file around...
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFBnPcXDsmuPPFOO2cRAnR1AJ9Vha96Z8s/KN2EIONy3nfZlLlxnQCfVXh2
z7ADxJYod501tENFm8PtN7k=
=ksnC
-----END PGP SIGNATURE-----
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
