On 9/5/06, Jim Hyslop <[EMAIL PROTECTED]> wrote:
-----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.

 
The problem with that approach is that I have to keep exporting the source everytime I do a code release which is frequent.  That would create a maintenance chore I don't want to have to deal with.

==================================================================
   Aaron Bono
   Aranya Software Technologies, Inc.
   http://www.aranya.com
   http://codeelixir.com
==================================================================
_______________________________________________
info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs

Reply via email to