   Project  Revision Control
  First off this question spans several topics and I wasn't sure what forum to post it in, so appoligies if this is the wrong form.I'm planning on writting some new tools this summer, which is basicly just an extensible project managment tool and I've come up with several inquerries about asset/source manangment and application updating.The idea is use different git branches for different things in the project. One branch would be dedicated to source code, one to media content, one to application packages, and one for content packaging. The application itself would only access the packaging branches. Does anyone have any experience using a similar system like this? If I embed a git client in the application will the application readily support delta encoding for content updates?Other thoughts are about game modding.. it should be possible to add mod repositories to the application and have it download and update mod content. How hard would it be to interface with git-hub, or sourceforge?(I'm also worried about local machine permissions blocking updates.. but I'm sure I can work around that if I use a user directory instead of a system's)   
Quote:Original post by TntrickerThe idea is use different git branches for different things in the project. One branch would be dedicated to source code, one to media content, one to application packages, and one for content packaging. The application itself would only access the packaging branches. Does anyone have any experience using a similar system like this? If I embed a git client in the application will the application readily support delta encoding for content updates?I'd beware of git client embeding unless you're dedicated to making this an open source project -- git is GPLed.If you do end up (ab)using branches like this, git headless is a useful command.  This is handy for creating GitHub Pages, for an example, where things are nominally related by what project they belong to, but otherwise unrelated.I'd be wary about going overboard with this though -- e.g. generating documentation from one branch from source code comments in another branch sounds like it would be a massive PITA.  Even something as simple as separating content out into it's own branch makes versioning issues a much more important factor.Quote:Other thoughts are about game modding.. it should be possible to add mod repositories to the application and have it download and update mod content. How hard would it be to interface with git-hub, or sourceforge?Github is pretty good about making nice APIs for you to access their stuff with.  Can't speak for sourceforge.  Can't say how easy it is to implement whatever you're envisioning, though, without knowing a lot more about what you're planning.   