Durk Talsma wrote:
> Given that we are taking this route now, FlightGear CVS is, I guess, cleared
> again for major and somewhat more risky commits (JSBSim sync, etc etc).
Alright, I've updated JSBSim now, including a number of engine files.
The following files might need some attention though, since they are not
in JSBSim CVS:
A6M2/Engines/CS-40B.xml
an2/Engines/ASH-62IR.xml
Boeing314/Engines/WrightGR-2600.xml
c150/Engines/eng_O-200.xml
C684/Engines/6Pfi.xml
dc6/Engines/eng_R-2800.xml
DR400/Engines/Lycoming_O-235-L2A.xml
Dragonfly/Engines/Rotax582.xml
ercoupe/Engines/c-75-12.xml
flash2a/Engines/503.xml
Noratlas/Engines/MarboreII.xml
ogel/Engines/200hp-jsbsim-2.0.xml
P-38-Lightning/Engines/Allison.xml
SenecaII/Engines/tsio360eb.xml
Skyranger/Engines/rotax.xml
Storch/Engines/Argus_As_10.xml
ZivkoEdge/Engines/io540.xml
Erik
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
