Re: How to keep developers separate from committers?

[Mark D. Baushke]

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

Jean-Christian Imbeault <address@hidden> writes:

> I had asked the sysadmin about using branches to make merging easier
> but he said that going that route would make it impossible to restrict
> the developer's access to just one branch.

Your sysadmin is mistaken.

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.

> What is a better approach to what we want to achieve, i.e. restricting
> access but making merging simple?

Use branches.

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

iD8DBQFA2n8n3x41pRYZE/gRAqaRAJ0TqkVmiv9NwJs9OQFWmAN5/8hiAACfa1Hg
ehHTEJuOItzLksGDhFVzYrc=
=awa5
-----END PGP SIGNATURE-----