× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



> From: Christopher Joseph
>
> Start here http://www.cvshome.org for relevent information regarding CVS
> use although I have NEVER found the information particularly clear.

I'm currently doing just that, using CVSNT for my server.  I posted a
question on IBM's mailing list but didn't get squat - maybe you can help?

I'm trying to determine the best way (well, the easiest) to transfer all the
information in my VAJ repository to a CVS repository.  I have several
versions of code, and I'm trying to keep that version information.

To date, the best I've been able to theorize (and I haven't even gotten this
to work in practice yet) is to set up a repository in CVS for each project,
then repetitively check everything out into work folders, export the next
version from VAJ into the same work folders, then check that back into CVS.

I'm still a complete neophyte, though, because I don't know whether I should
use separate repositories, or simply separate modules for each of my VAJ
projects.  My guess is that it really depends on how closely related the
projects are.  For example, I have four closely related projects (internal
classes, external interface, and a couple of test environments).  Those seem
to make sense as separate modules within a single repository.

I don't know anything about module lists; it looks like I have to manually
create them for each module.  Are module lists suggested?  Required?  Not
required but highly recommended?

This is all great fun!  However, I could use tons more information.  Any
pointers to basic CVS information is fine, especially modules.

Joe


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.