Revision Control System

[Dax]

Do you use a revision control system such as subversion or CVS while developing your operating system?

I'm not, but that's about to change. After browsing the web I stumbled upon darcs, it's a distributed based system instead of a client/server based system like subversion. I'm not really into all of this, well, I've used subversion before, but I'm still a noob using it.

Has someone used darcs before? And what would you advise me to use?

[bluecode]

Do you use a revision control system such as subversion or CVS while developing your operating system?

Yes, subversion. There is free svn hosting at sourceforge and at opensvn.csie.org.

[Candy]

I'm using subversion at the moment for keeping all my files safe from any computer crash. It's on the SF svn server, my home computers (2 of them) and my USB stick which I carry on me at about all times. It allows me to just check in something and be sure it's not lost, check out a full tree anywhere and go about developing (aside from the compilers, but since it hasn't compiled for a few years that's kind of ok).

For the record, working on getting it compiling again right now.

[ces_mohab]

Because my project is hosted at sourceforge i used CVS system with netbeans or eclipse. I think the main purpose of CVS is to provide a safe place of source code.
I didn't get benefit from version control system.

[durand]

I use darcs. I far prefer it to subversion but you will have a hard time setting up an online repository to which you can push your patches unless you have ssh access and the ability to run darcs remotely.

darcs is distributed development with more focus on multiple repositories between which patches are shared. You can call one of them "official" and then everyone can agree to pull and push the latest patches from that one.

svn/cvs mostly needs a central repository on which everyone will work.

svn/cvs has a lot of free hosting everywhere and will be better if you plan to make use of them and to have a few people working on your project without you needing to process all patches.

[Candy]

One thing I've noticed with svn (today):

When you remove a bunch of directories recursively, it fails on the directory remove if the dir still exists when you commit it. All other commands work just plain by putting svn in front of the command, except for mv and rm (since both fail on the checkin).

Solution: rm -rf the dirs before committing. Still, it's annoying.

[Hadrien]

I'm using Subversion & Trac on a private server and TortoiseSVN for the client on Windows. Those are tools I enjoy in comparison with what I have been using elsewhere.

[Combuster]

I use CVS for sharing source between places, as well as to keep backups just in case. No expert usage, really