> By the way, I committed the changes to releases/2.2.0 and then merged that
> branch into next. This is the way fixes should move between the two branches.
> Please don't commit a fix to next and then cherry-pick it to the release
> branch. It is very messy to have the same change committed on several
> different branches.
I tried that on the data repo without luck. Many Aircraft are removed for the
release, and merging propagate that in master.
Recovering my local workspace now...
Regards,
-Fred
--
Frédéric Bouvier
http://www.youtube.com/user/fgfred64 Videos
------------------------------------------------------------------------------
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
