On Mon, Jan 24, 2011 at 9:01 PM, Curtis Olson wrote: > If I do a build of the "next" branch, > then switch to the releases/2.2.0 branch, I still inherit all the build > object files from the other branch. So then I have to do a complete make > clean; make for simgear and flightgear each time I want to jump from one > branch to the other
I don't have a GIT answer to your question - but I'm surprised you need to "make clean". Switching branches results in all changed/switched source files getting fresh timestamps - so the normal make dependency rules trigger a rebuild for the affected objects. And unless the branches diverge too much, it should be much quicker than a full rebuild. I'm curious though if there was a better GIT workflow (you're never finished with learning about GIT...). cheers, Thorsten ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
