-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Aaron Bono wrote: > 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.
Hmmm... in that case, have you considered simply exporting the source code to a non-CVS directory these people can read? It seems to me that will be easier to manage in the long run. Just a thought. - -- Jim Hyslop Dreampossible: Better software. Simply. http://www.dreampossible.ca Consulting * Mentoring * Training in C/C++ * OOD * SW Development & Practices * Version Management -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFE/ihBLdDyDwyJw+MRApZuAJkB/pfLs0+WMmkzum9X5wWRZk+EaQCcDoR0 xkSx16qqT30PqwHZcFGL7oA= =sg5L -----END PGP SIGNATURE----- _______________________________________________ info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
