Re: How to keep developers separate from committers?

[Mark D. Baushke]

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

Jim.Hyslop <address@hidden> writes:

> Mark D. Baushke wrote:
> > The commitinfo trigger is able to run
> > 
> >     cvs -Qn status
> > 
> > on the list of files and determine the 'Sticky Tag:' line 
> > that relates to the file being committed.
> Will this also work with a remote checkin? 

Yes.

> The docs
> (https://www.cvshome.org/docs/manual/cvs-1.11.16/cvs_18.html#SEC169)
> say that it works with a copy of the workspace on the server, but they
> don't say exactly how that copy is made. 

When the local cvs determines that a file is a candidate for being
committed, it creates a copy of just the 'modified' files on the server
including the CVS/Entries CVS/Tag CVS/Repository and a CVS/Root for the
server-side tree being committed.

> Does it use the same sticky tag as the local workspace?

Yes.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFA2vee3x41pRYZE/gRAkLeAKDkOsDhPLBWhF7whnYdyJ/1Uas6PACgjOn8
P2hCklHWja7LzsbYh3LPQ30=
=NY6m
-----END PGP SIGNATURE-----