pouët.net

I use CVSDude for the repository and Tortoise explorer plugin to control it. I've had no problems with this setup and have used it for over two years now...

WTF? 2009 sure is going to be a strange year.

We've reached page 2 and this thread still is useful and not pouetized.

The only important thing is NOT to use CPOLD :
http://roland.entierement.nu/blog/2008/01/22/cpold-la-poudre-verte-du-suivi-de-versions.html
(in french)

... the only exception is if you are coding with La Rache method :
www.la-rache.com
(also in french)

Everything else is better :)

We worked with CVS for years but subversion simply feels superior now. We also started to use it for art assets and coupled with tortoisesvn this is just a great solution!

I'm extremely far from being an expert on version control, but my impression is that people prefer distributed version control systems these days, and that generally people seem to like git. Personally I use darcs (well, the word "use" is maybe an exaggeration; bad habits die slow...)

There is nothing which prevent you to have a centralized server with DVCS systems. As you can imagine, every largish project have a centralized server. However, with a DVCS you can work offline, too.

what about dropbox? It synchronizes to the web automatically. Ok, you only have 1 folder on the disk to put everything inside but I think at least for personal projects its quite perfect. Has automatic versioning and sharing implemented already.

getdropbox.com

rumor has it git is the new svn

perforce (p4) above all

i agree with niels. Perforce!

we used cvs in the past but svn (subversion) is better which we use now. available everywhere and free. with turtoisesvn lazy windows users can be eased as well.

i use subversion and love it

I also use Perforce for my personal development. It's free for a two clients configuration.

And for the "large source", having versioning and comments for each revision is still quite nice:



A source control/revision system is not only for archiving versions, it should also help you find out what happened between versions, and allow easy-rollback, support moving files, etc...

see also http://www.pouet.net/topic.php?which=4545 for more answers

yes, we are all the time discussing the same stuff in new different threads. Like with the famous "why demosceners prefer windows over linux" variations, I'm sure one day soon somebody will create a new thread like that for a fourth time.

That merge tool looks nice ^

svn here

Been using CVS, SVN and Perforce - both personally and professionally. I (also) recommend SVN for its intuitive usage and it solves conflicts very well. Also for Windows, by using VisualSVN it is really quick job to install and setup your own svn server.

subversion+tortoise. I tried using Ankh to integrate svn into visual studio, but it turned out be annoying. can't remember exactly why at the moment.

Also Linus Torvalds hates CVS , subversion, perforce etc with a passion. Surely his needs may differ from yours and mine though. Interesting talk nonetheless.

Paralax: You can remove the "may" from your sentence. The Linux kernel team process is very different of the one used on let's say a large video game development.

On the Kernel, the few gurus have a deep knowledge of what's what in their very specific area, while on a video games there are gazilions of very different things (gui, network code, gameplay code, scripts, shader data, etc...) so most of the time you integrate branches that contains things you don't know about, plus the whole thing has to be kept in sync with the bug/job-tracking system, validate by QA people who need to track if a particular issue is in a particular version, etc...

Git is conceptually nice, but I doubt it's adapted to all and every body's processes.

Personally, I hate more the languages we are using than the source control systems. Having the program written as text in one or more files that are more or less dependents of each others is a remnant of the past, and I hope it will get replaced by something better soon.

dbug, my guess is that a kernel consist of more than a few modules and thus your own argument works in favor of a concurrent versioning system on kernel development :-)

Ok, I correct what I wrote, instead of "Git is conceptually nice, but I doubt it's adapted to all and every body's processes." replace by "The Linux kernel development process can't be applied on every project".

The tool itself was not the problem :)

Thanks to whoever it was posted about Dropbox! Not full-fledgedversion control, but very quick-and-easy solution to the issue of synchronizing between several workstations.

me! :D
yea dropbox is the shit.
But professionally we use SVN as well. tortoiseSVN is quite cool.

i've smacked myself over the head multiple times (had to use svn/tortoise for 6 months) repeatedly out of pure agony -- exactly what is cool about it?

it must be the first sourcecontrol system youre using or? :)