Hanser, Kevin [EMAIL PROTECTED] writes:
My boss seems to think it would be a good idea to share our CVS root so we
can easily browse it. I don't think this is a good idea... can anyone give
me the pro's or con's of doing this?
If it's read-only, there wouldn't be much harm...
We have our cvs
My boss seems to think it would be a good idea to share our CVS root so we
can easily browse it. I don't think this is a good idea... can anyone give
me the pro's or con's of doing this?
We have our cvs repository located on a linux box, and are using winCVS to
do our checkouts/updates/commits,
Hanser, Kevin wrote:
My boss seems to think it would be a good idea to share our CVS root so we
can easily browse it. I don't think this is a good idea... can anyone give
me the pro's or con's of doing this?
The repository root ($CVSROOT) is useless for browsing since you're looking at
it in a few
minutes two days ago. Jcvslet is a servlet so you'll need a servlet
container like tomcat (http://jakarta.apache.org/tomcat/index.html) to run
it.
Cheers,
Mirco
From: Hanser, Kevin [EMAIL PROTECTED]
To: '[EMAIL PROTECTED]' [EMAIL PROTECTED]
Subject: sharing cvs root?
Date: Wed, 13 Mar
They want to actually be in the repository? No, that is a bad idea. You
should explain to your boss the reason for a source code repository.
If that is the case, get them ViewCVS http://viewcvs.sourceforge.net/ and
CVSgraph (link is on viewcvs site). They will get used to it.
In the
My boss seems to think it would be a good idea to share our CVS root
He is ignorant. Keep him away!
can anyone give
me the pro's or con's of doing this?
No pros, lots of cons.
Does he also like to see raw database files instead of using a database
client? No. Does he also like to see
