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

[Derek Robert Price]

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

Greg A. Woods wrote:

> There is no trigger for "cvs rm" and there MUST _NOT_ be.
>
> There is no trigger for "cvs add" and there MUST _NOT_ be.


I have to admit, there is a certain logic to drawing the line at
triggers for repository changes, not workspace changes.  The user
should have total control over their workspace and the server
shouldn't be able to veto anything except changes to the repository.

This still requires that `cvs add' of directories not alter the
repository until commit.  It also reminds me that allowing `cvs add'
and `cvs rm' in a workspace without even write privs to the server has
been on my wish list for quite awhile (this enables complete patches
to be generated from a public repository by anybody).  I'm guessing
the proposal Greg is advocating would provide for this.

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.

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

iD8DBQFBnPCfLD1OTBfyMaQRAqsWAJ4hbqIedBH7fhcBXeNnErm/PXEsNQCfUgKo
Wv/HTA9wD1ZjrLPc4CMjB2k=
=GKMh
-----END PGP SIGNATURE-----