[Top][All Lists]

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

RE: Getting started with WinCvs B4

From: Arthur Barrett
Subject: RE: Getting started with WinCvs B4
Date: Fri, 21 Oct 2005 08:04:58 +1000

This is not the correct list for WinCVS.

The CvsGUI list is here:

>From your description you are using CVS in local mode - which is not how
you want to use it in a team.  WinCVS includes CVSNT client, the (free)
server and more info is here:

Depending on your past experience with SCM tools you may find WinCVS or
another CVS gui to be more suitable for your working style.


Arthur Barrett

-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of Adam Sandler
Sent: Friday, 21 October 2005 3:40 AM
To: address@hidden
Subject: Getting started with WinCvs B4


I have a question about WinCvs B4.  In past lives, I've used
big, expensive, commercial source control applications.  The project I'm
currently on has no such resources and I'm trying to take WinCvs out for
a spin to see if it can help us out with versioning and source control.

I've tried to read as much of the documentation as I can find but it
hasn't completely helped.  For one thing, the documentation the WinCvs
ships with is the same unix documentation that is found on sourceforge.
While I know enough about unix to be dangerous, we develop projects for
Windows and as such I need a Windows solution.  There's not a 100%
equivalent of performing an action between both OSes.  And the message
windows which pop up in WinCvs are not always entirely accurate either
(e.g., the dialog describing the syntax of setting the root is incorrect
in WinCvs).

At any rate, I've successfully set the root as c:\cvsroot and then
created a new repository.  That action put another folder called cvsroot
in the c:\cvsroot directory.

If I try to import the current location of a project, it copies existing
folder into c:\cvsroot\cvsroot.  This is where I really get confused...
shouldn't importing just create a reference to a location, why does it
physically copy/move the files?  If I try to check out that project, a
form appears which asks for the output location?  Why can't I just work
in the repository area?  Why does the app ask for an output location?
So do I have three areas on the file system now with three separate
copies of the same project?

The documentation I've read doesn't clear this up at all.  Either
directions to relevant docs or if anyone can shed some light on how they
check stuff in and out on a daily basis using WinCvs is greatly


Info-cvs mailing list

reply via email to

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