Re: [Cxtable-devel] OK...that turned out to be easier than I thought...

[Borne Goodman-M. <bm...@eg...>]

Actually I usually find it best to check in configuration / build /
script files into the code base, because they usually evolve with the
rest of the code and you want to have a complete set of files that a
user can use to build / run the system.

Now that you got the cxtable tree, whenever you do ANY chages to the
files, or add new ones, make sure to do it in there.  Once you are done
making a "set" of changes and testing them to make sure all works well,
run > cvs ci (or cvs commit) to commit your changes to the CVS server.

If you don't make any changes for a while, and thing someone else may
have, before you start making changes run >cvs update -d (the -d to get
new directories that might have been created).  And this will merge the
new code on the CVS server with your local code base.

I have a good book on CVS, but it is at home so I don't have the title
here, but suggest you might want to get one, or at least read up on CVS
a bit.  The version control system is very important to a project,
especially if we want to do tagging and branching.

--bjgm

On Tue, 2001-12-04 at 01:31, David Scott Williams wrote:
> (Ps- You could've left off the .bat and .doc files ;-) )
> 
> I updated my "tree" from the site...
> 
> What next?
> 
> --
> ~Dave
> xi...@pr...
> http://sourceforge.net/projects/cxtable >The xTable Project<
> http://sourceforge.net/projects/dustyscript  >Dustyscript Child Script
> Language<
> 
>  |>>weblog: http://www.geocities.com/xiarcel/weblogs/log.html<<|
> 
> "He who trades even a small amount of freedom for temporary security
>  deserves neither freedom, nor security"
>   -Benjamin Franklin
> 
> "When I think back on all the crap I learned in High School...
> it's a wonder I can think at all..."
>   -Paul Simon, "Kodachrome"
> 
> 
> 
> _______________________________________________
> Cxtable-devel mailing list
> Cxt...@li...
> https://lists.sourceforge.net/lists/listinfo/cxtable-devel
>