There are more and more aircraft in CVS with two *-set.xml
files, where one is basically empty and only referring to
a second one. This is understandable in cases where actually
more than one FDM is used or very likely to be used in the
next time. But it's becoming a problem if this redundant
stuff
Melchior FRANZ wrote:
> There are more and more aircraft in CVS with two *-set.xml
> files, where one is basically empty and only referring to
> a second one. This is understandable in cases where actually
> more than one FDM is used or very likely to be used in the
> next time. But it's becoming a
Melchior Franz wrote
> Sent: 19 April 2008 07:57
> To: flightgear-devel@lists.sourceforge.net
> Subject: [Flightgear-devel] foo-set.xml -> foo-yasim-set.xml
>
>
> There are more and more aircraft in CVS with two *-set.xml
> files, where one is basically empty and only
* Syd -- Saturday 19 April 2008:
> can you name an example so I can see what you mean ? My vote would
> be to do something about it , so if mine are like this [...]
I haven't looked closely, but I didn't refer to your aircraft.
You get a good impression if you try this:
$ ls $FG_ROOT/Aircraft/
On sam 19 avril 2008, Melchior FRANZ wrote:
> There are more and more aircraft in CVS with two *-set.xml
> files, where one is basically empty and only referring to
> a second one. This is understandable in cases where actually
> more than one FDM is used or very likely to be used in the
> next tim
5 matches
Mail list logo
