Since I started tinkering with ecuflash I have ended up with a few rom files that I try to keep track of by date and file names. I was wondering if anyone was using any sort of versioning system to keep track of their files.
I currently use sugarsync (an alternative to dropbox which I also use) to sync the roms between my desktop and laptop. I am hoping someone can recommend something that is portable and fairly easy to use, preferably with a gui frontend.

 

I don't use any Dropbox-like service to keep my roms synchornized between laptop and desktop, however I do use the following naming scheme:

{first name initial}{last-name initial}_{rom number}_{changes that I made in this map compared to the previous}

For example, my current rom is:

EB_266_altFuel-altTiming.bin

 

Thanks raptord, cant go wrong with the k.i.s.s. approach. I was looking into something more complex so that I could keep much more detailed notes. I am testing some software now but I am using the filename method as a backup.

 

Have you tried something like Mercurial? It might be overkill for just keeping track of roms but when you commit a change you add notes to say what you changed in the new version (In this case you'd commit after every new rom and add notes that would pertain to that rom).

 

I use Dropbox to sync all of my logs and roms. Works like a charm!

-Acree

 

I looked at it, right now I am trying bazaar http://bazaar.canonical.com/en/ So far so good. I am going to see how it behaves over the next few days.

 

I just compress/zip matching bin and xml's and give it a long cryptic name

 

I initial, date, and give a one or two word description on the change. And everything is done on my laptop with backups on my desktop once in a while.

 

managing by filename seemsto be the most popular option. I guess it makes sense since all the versioning software expects written code and cant seem to handle .bin files.

 

Why not use dropbox to manage the location of the ROMs as well as creating an Excel file that gives you a brief description of what you've changed on each Rom.

For example say one ROM is XX_226, in Excel have a column that says the ROM name that you saved the file as in addition to a description section stating the changes you've made.

 

I'd be waaaaay too lazy to open up my excel file and update it with the relevant rom information. That's why I put it directly in the file name

 

That's Windows Explorer for me, detail view, sorted by date
My 'backup' system is a netbook->thumb drive->3monitor desktop... since I cant stand working on a netbook

 

Coming from software engineering I've very familiar with SVN as a code repo ... using SVN (or other like GIT, etc) for managing ROMs works pretty well for me.

Each ROM can be 'checked out' modified and then 'commit' back to the repo with log of what change was mode ... all the logs will be stored and you can track all the changes that you or others made over time. Any computer with access to the repo can 'update' their local snapshot and make sure that it pulls down the latest versions.

 

BTW I'm also a software developer, but unlike most I dont think much of 'version control softwares'
If you really want a good version control approach, use Excel... insert links to your zip/folder with bin/xml/logs, add list of mods, add screenshots of maps, logs, virtualdyno plots, speeding tickets, etc

 

"This map is crap, I got 3 more speeding tickets than with the last one!"