-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Arthur Barrett wrote:
> Aaron,
>
>
>>In essence, I want CVS to allow the client
>>to connect to what they think is the trunk
>>but instead get the specified branch.
>
>
> Why?
[...]
> At a more practical level, if you did this and the user started to
> create reports on the repository for changes to "all branches" they'd
> get awfully confused when they saw all their changes appearing on
> another branch not the trunk.
Aaron, consider also the headaches and major confusion that will arise
when these users start talking to other users about "the trunk" - which
trunk do they mean, the real trunk, or the trunk they see? Sounds like a
recipe for disaster to me.
There is no chance they will talk about the trunk - the users I give such access to will have no concept of the trunk. The access I am looking for is something where the user connecting will only want to view the current code in production which is stored on a very specific branch. They will not want history, they will not want to commit changes, they will not want to know what CVS even is.
I want to allow users to connect to the branch without having to specify the branch - that is just one more thing for the client to forget or mis-type which creates support issues for me.