Re: [Algorithms] Tools (was Manual Pages)

[Ray <ra...@gu...>]

Kamil Burzynski wrote:
> 
> ----- Original Message -----
> From: "akbar A." <sye...@ea...>
> 
> > here, found the link to the cvs -gui front end in windows.
> > looks very nice
> > http://www.wincvs.org/
> > i don't have WINE running so can't test it ;|
> 
> We are using WinCVS on winblows every day and it seems to be very good - ie.
> frontend itself is quite bug-less, and
> using it is not a pain. Very good integration with tcl/tk - we're adding our
> own scripts to it and them works fine. If you're using
> windows and cvs WinCVS is definitely good choice imho.
> 
> PS. Why you're arguing about multiple checkouts? Rule is simple: if you want
> to modify file check it out and lock it - nobody else
> will change it in meantime. If two or more person REALLy need to work on the
> same file at one time - this is clear sign to split file
> in two parts. With repsect to this rule multiple checkouts are no problem
> anymore - we're using it every day and don't conmplain at all.

We here use raw commandline CVS for windows, *nix, and macos9/X
Haven't had any problems.
We don't use it for binary files, just source code.
We just have a netowork share that the artist(s) use for now, but since
we only have 1 fulltime artist, it's not a problem yet.

For CVS we use the cvs update and cvs commit paradigm.
we CVS co and then update or commit when we change stuff and allow cvs
to do the merging. CVS forces us to update before committing and it
won't commit files that have conflicts in the merge, so that makes it
nice.

I used to use sourcesafe at my previous job and it was ok. It was slower
than cvs but it allowed one to not be able to modify a file without
checking it out and you can check out files from visual studio.
But since we use cvs now and technically always have all files checked
out, I don't have to worry about integration into vc++.

My 2 cents.

- Ray