On 08.02.2011 20:40, Torsten Dreyer wrote:
> No sweat - 2.2.0 is not affected. This is because of the TankProperties
> I'll try to come up with a solution but that might not be before the weekend.
And, always seeing the positive side, this might be a great opportunity
to have more people testing the current 2.2.0 branch. We're preparing
for the release - and since GIT/next has already moved ahead, it is no
longer a valid test case for 2.2.0.
Switching branches is easy and quick - of course, thanks to GIT :).
To create a new local 2.2.0 branch (needed for simgear and flightgear):
git checkout -b releases/2.2.0 origin/releases/2.2.0
You can then switch between the next and 2.2.0 branches by:
git checkout next
and
git checkout releases/2.2.0
Remember to keep each branch updated using "git pull".
Finally, rebuild normally (e.g. "make && make install" for simgear and
flightgear).
Yes, there's also an advanced method using separate, cloned repositories
- if you want to be able to run both versions without the need of
switching and recompiling. See the flightgear-devel archives...
cheers,
Thorsten
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
