Revision Control System?
 

Has anyone ever proposed using some sort of revision control system to track the various ROM changes?

I realize that some of the changes are binary edits, but tracking the .rgu files (did I name that correctly) might make life easier on everyone.

There could be 1 CVS/SVN "module" for a base kitchen and then a "module" for each OEM item - that way one could checkout the kitchen and then checkout individual OEM modules as needed into their kitchen.

I'm not sure how such an idea would go over - the ecosystem here seems to mostly work, but individually tracking all the various versions and things going on with customized versions is a little confusing for us new people.

Personalized/Test customizations could be branches and then be merged back into a stable main line, etc. Nightly snapshots could be created for those not wanting to learn the CVS/SVN fu.

I know this might be all too serious, given that MS has been cracking down on ROM hackers. I just know that my phone is so much more pleasant to use since finding this site - I just think that some dev discipline might be helpful.


...tom

Well, that would probably be one of the steps if the idea of the group kitchen project goes forward (flog flog flog). The thing is, at the moment, everybody's going their own way, and the sharing of ideas is sporadic at best. As such, there really is no main baseline for creating such a code repository mechanism.