Hi, Martin Spott wrote: > Thus, if you'd be willing to put your stuff into a branch at the main > repo, please go ahead - call us if you don't have write access.
I don't feel too good about adding even more branches directly into the main TG repo. The reason is this: In the process of the 850 development we have changed and rebased the history multiple times against TG master (mainly because of the cmake addition that came along and that I added to our files as well). This as a consequence changes the git objects and needs a forced push. That's allright for testing. I'd rather do the dirty work seperately in an own repo than polluting the TG main repo with old and unused git objects (which git does not throw away by itself). And no, I'd not use git merge for this, as this as it complicates the history and leads to all kind of problems later on. To make life a bit easier, I have moved the TG 850 repo to be a clone of TG now, so that at least activity in our clone shows up on the main FG page. This should already improve the situation quite a bit. Chris ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
