Version Control and Romhacking

[RedComet]

So I've recently discovered the miracle of revision control (yeah, I know I'm  late to the party ) and I'm wondering if anyone uses it for their romhacking projects? I know I'm definitely going to be using some sort of revision control from here on. Not looking for suggestions or anything.  I just wanna see what people are doing.

[Ryusui]

For Breath of Fire 2, I just saved old versions of my patch to separate directories. >_>

With Nanashi no Game, the project mastermind had a freakin' SVN set up. Took some getting used to, but worked pretty well. :3

[Gideon Zhi]

I just wanna see what people are doing.

My project structure hasn't changed since... god, since probably before Front Mission Gun Hazard in 2003. And you've seen what it looks like (i.e. a mess.) But it's what I'm comfortable with, so nyaaaaah!

[KC]

I use SVN for all my projects, too. It's very handy, if you take enough care and commit changes often. You will have an easy time figuring out where any issues were implemented, as you can go back to any previous version with just a few clicks.
It's of course also useful for exchanging data. Give everyone involved access to the repository and you'll never have to manually send or replace files again, you just update and it's there. I also give the translators all the necessary data so that they can always build the most recent version of the game themselves, allowing them to test changes right away.

[Nagato]

Deleted.

[MathOnNapkins]

I've recently begun using it, and I have to say I'd have a hard time going back to not using it. Even if I don't use a lot of the features, I really hate losing work (I lost a week's worth once). And with TortoiseSVN being so easy to use on Windows, there's really little reason not to. I also hear git is pretty easy to use too, though I'm not very familiar with it. I used to back things up between computers with a USB drive and manually merge changes to keep things up to date, while making full backups occasionally as my only history. That is such a chore compared to just comitting some changes and being done with it.

[justin3009]

I need to find a better organization method.  All I do is just have multiple copies of the file dictating what day and time it was last modified.  If anything else is necessary, I add a short description to the file name as well.

[DaMarsMan]

I used to use SVN but once I started using git/mercurial I'll never go back... All my rom hacking projects are revision controlled.

[rastsan]

Haven't used svn.  Thinking about using it for the 6 or 7 projects I am just the hacker for.  Though implementing that for nds files may be challenging for those who only translate text/spreadsheet files and image editors who won't work with any other software other than their preferred image editor. 
Strangely its only the projects that I don't really do anything but insert others work that this might be useful for. 

I prefer to debug after every change for my own projects though.  If any problems arise I want to fix them right away and not deal with them later.   
I think I may stick with an image and text repository. 

[Pennywise]

I actually setup a SVN with Assembla, but I haven't actually used it and in fact Assembla keeps telling that they're going to delete it for it several months now. I'll probably never use the SVN as I have yet to do something stupid and haven't really lost or saved over any of my work.

[Spikeman]

I'm going to second the recommendation of Git over SVN. You might check out the Open Source rom hacking thread I made recently, there's a lot of links to projects, so you can get a good idea of how things are laid out.

Also check out my signature, there's a few links to my projects hosted on Github.