Re: add hook question (was Re: Problem with importing third-partysources and adding/committing changes)

[Derek Robert Price]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Todd Denniston wrote:

>>I also still would not object to the a `cvs add -C' "convenience" hook
>>which requested that the client contact the server and validate the
>>add.  Any team that valued this option significantly should find it
>>fairly easy to enforce a policy of placing `add -C' in users' .cvsrc
>>files.
>
>
>I agree that this would be a nice _additional_ patch so the user could


Absolutely.  I intended this as a suggestion for a potential
additional patch which I would find acceptable if submitted.  I in no
way meant to imply that it be a condition for acceptance of any patch
generated as a result of Greg's proposal.

>validate early on that their information would go in, as it would
only require
>contacting the server in the case of sites where the users know the
repository
>admin has such rules in place, and commit would allow the ENFORCEMENT
of those
>rules. I suspect that a determined user could fake enough information
into the
>CVS/* files to get around the add, but it should be much more
difficult to get
>around commitinfo because all files at that point are under the cvs
server's
>control.


Exactly.

Cheers,

Derek

- --
                *8^)

Email: address@hidden

Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBnPhzLD1OTBfyMaQRAki7AJ9YaLWKRJ27ut92CRB3SbJ8RLDvBACeNViR
4AX2p3ruMlYSBKDf0uW3Cgk=
=l83S
-----END PGP SIGNATURE-----