Hi,
Just a heads up.
I always wondered why so many accounts with very suspicious names were being
created on the Wiki.
I think the answer is clear now, someone is trying to place "traps" for the
unwary with links pointing to rogue pages:
http://wiki.flightgear.org/index.php/Special:RecentChanges
On 01/26/2011 01:31 PM, Anders Gidenstam wrote:
On Tue, 25 Jan 2011, dave perry wrote:
I have tried to load several AC that did not load with "filed to load
" errors. So I did a survey of the entire up-to-date
fgdata. I used an up-to-date fgrun and went through all the AC.
The following do n
On Tue, 2011-01-25 at 23:41 -0700, jac...@lfstech.com wrote:
> How about a show of hands? Is there enough interest and volunteers to
> organize a team to tackle the problem?
As I said in my original post, I'm not a programmer so, unfortunately, I
couldn't help in that regard. However, I'd be wil
On Wed, Jan 26, 2011 at 6:28 PM, Heiko Schulz wrote:
> Sounds great- but do you know this already?:
> http://www.gitorious.org/syd-s-flightgear-content/777-200er
>
> You might wanna try a merge request
>
> Cheers
> Heiko
Nope, I didn't know about that one. Thanks. :)
cheers
--Jacob
---
Hi,
> This is for Syd really. There is
> topic on the forum about improving
> the 777 FDM, and I myself got a bit carried away with
> modifying the
> ground steering. Attached is a diff of my changes against
> git master,
> as well as a zip file containing (hopefully) all the
> modified files.
>
Hi Bertrand,
Here are a couple quick responses:
- The reason JSBSim would want to keep a copy of the glue code would be to
serve as an example for others who want to integrate JSBSim into their
projects.
- Changing the name of the glue code (I guess I missed seeing that this was
officially decid
Hi,
> On Tue, 25 Jan 2011, dave perry
> wrote:
>
> > I have tried to load several AC that did not load with
> "filed to load
> > " errors. So I did a survey of
> the entire up-to-date
> > fgdata. I used an up-to-date fgrun and went
> through all the AC.
> >
> > The following do not load even t
On Wed, Jan 26, 2011 at 1:21 AM, Stefan Seifert wrote:
> Well you don't. Often you just can leave modified files in place while
> switching
> branches. If it's not working, you still can simply git stash before
> switching. git stash creates a temporary branch and commits your local
> changes
> t
2011/1/26 Erik Hofman :
>
> After a bit of discussion it was decided that the FlightGear/JSBSim glue
> code in JSBSim.[ch]xx located in FlightGear/src/FDM/JSBSim now is
> maintained by FlightGear developers instead of by JSBSim developers and
> therefore these files will not be overwritten in futur
I just sent you a message to what is likely an old and replaced address.
Just wondering if you are still going to come up to do your thing at LUGOD?
jj
--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD valu
On Tue, 25 Jan 2011, dave perry wrote:
> I have tried to load several AC that did not load with "filed to load
> " errors. So I did a survey of the entire up-to-date
> fgdata. I used an up-to-date fgrun and went through all the AC.
>
> The following do not load even to the viewer in fgrun:
> 737
[saw this in time to de-lurk]
On 01/25/2011 11:22 AM, Anders Gidenstam wrote:
> I suspect the option --local to git clone might be useful.
> I have not tried myself, though.
Yeah, this is the best answer for this kind of problem.
The .git directory ends up being near-zero size (so long as the de
On Wed, 2011-01-26 at 07:19 -0600, Jon S. Berndt wrote:
> I have received and applied patches from several places recently. Make sure
> that patches are not accidentally reversed.
They won't since the patches at the FlightGear side will be overwritten
by what JSBSim had in CVS.
> It is very impo
On 26 Jan 2011, at 12:26, Erik Hofman wrote:
>> Great, that simplifies things considerably, hopefully for everyone. There's
>> still the issue of my FGPropulsion change, and Andreas' FGPropogate fix to
>> go into JSBSim proper.
>
> I've committed Andreas' FGPropogate fix in JSBSim, your fix ne
> -Original Message-
> From: Erik Hofman [mailto:e...@ehofman.com]
> Sent: Wednesday, January 26, 2011 5:55 AM
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] JSBSim merge
>
> On Mon, 2011-01-24 at 15:40 +, James Turner wrote:
>
> > Okay - I'm going to re-app
On Wed, 2011-01-26 at 12:23 +, James Turner wrote:
> On 26 Jan 2011, at 11:55, Erik Hofman wrote:
>
> > After a bit of discussion it was decided that the FlightGear/JSBSim glue
> > code in JSBSim.[ch]xx located in FlightGear/src/FDM/JSBSim now is
> > maintained by FlightGear developers instead
On 26 Jan 2011, at 11:55, Erik Hofman wrote:
> After a bit of discussion it was decided that the FlightGear/JSBSim glue
> code in JSBSim.[ch]xx located in FlightGear/src/FDM/JSBSim now is
> maintained by FlightGear developers instead of by JSBSim developers and
> therefore these files will not be
On Mon, 2011-01-24 at 15:40 +, James Turner wrote:
> Okay - I'm going to re-apply my patches locally, and also apply Andreas
> Gaeb's NaN fixes (and to the release branch too), but of course they all need
> to be merged to JSBSim proper.
After a bit of discussion it was decided that the Fli
On Wed, 26 Jan 2011 09:56:41 + (UTC), Martin wrote in message
:
> Chris,
> I think the benefit of having sort of a VATSIM-interface or -bridge
> for FlightGear is pretty much unquestioned, therefore I'll leave these
> details out. The point is a completely different one and probably
> consist
Chris,
I think the benefit of having sort of a VATSIM-interface or -bridge for
FlightGear is pretty much unquestioned, therefore I'll leave these
details out. The point is a completely different one and probably
consist of just two simple parts:
1.) Like probably almost every other OpenSource proj
Curtis Olson wrote:
> The other implication here is that it would be extremely handy to have
> multiple branches checked out simultaneously for other reasons. git makes
> branching easy, yes, but if you find yourself bouncing between branches with
> changes for separate projects, and external eve
21 matches
Mail list logo
