[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS Proxy

From: Aaron Bono
Subject: Re: CVS Proxy
Date: Thu, 7 Sep 2006 14:09:44 -0500

On 9/7/06, Todd Denniston <address@hidden> wrote:
Aaron Bono wrote:
> On 9/5/06, Jim Hyslop <address@hidden> wrote:
>> 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.
instead of exporting, how about having a special user keep a copy
of the correct branch(es) checked out?

That may be the approach we end up taking.  We could even set up a cron/scheduled task on a client's server to pull the code down to an internal location so they can look all they want and not mess anything up.

I am still curious if any of the other methods I mentioned, however unrecommended they may be, would be doable.

   Aaron Bono
   Aranya Software Technologies, Inc.
reply via email to

[Prev in Thread] Current Thread [Next in Thread]