> I just finished creating the release and placed the tar files on my server.
> Due to the capacity limitations of my own server, I'm not providing a
> download link here. They will hopefully shortly be transfered to the
> mirrors, shortly. I've also given the people involved in building the
> wind
On Saturday 15 December 2007 20:27:26 AnMaster wrote:
> Both me and AJ had that problem.
Yes, but it's dealt with in CVS now - Camel is good to go now, in my view.
Cheers,
AJ
-
SF.Net email is sponsored by:
Check out the ne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Vivian Meazza wrote:
> And there is a major issue with the chrome shader in the Camel - seems as if
> it makes the windscreen opaque in some systems - but not here.
>
> Vivian
>
Both me and AJ had that problem.
Regards,
Arvid Norlander
-BEGI
Durk Talsma
> Sent: 15 December 2007 20:07
> To: FlightGear developers discussions
> Subject: Re: [Flightgear-devel] Release in progress
>
>
> On Saturday 15 December 2007 20:46, Melchior FRANZ wrote:
> > * AnMaster -- Saturday 15 December 2007:
> > >
On Sat, 15 Dec 2007 21:06:55 +0100
Durk Talsma <[EMAIL PROTECTED]> wrote:
> On Saturday 15 December 2007 20:46, Melchior FRANZ wrote:
> > * AnMaster -- Saturday 15 December 2007:
> > > Yes but tar ball have been made [...]
> >
> > But they aren't released. Can still be fixed.
> >
>
> Agreed. The
On Saturday 15 December 2007 20:46, Melchior FRANZ wrote:
> * AnMaster -- Saturday 15 December 2007:
> > Yes but tar ball have been made [...]
>
> But they aren't released. Can still be fixed.
>
Agreed. The missing file has already been committed by Syd Adams. Now I'm
getting the following:
WAR
On Sat, 15 Dec 2007 20:30:00 +0100
AnMaster <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> IIRC the Beaver was included. But as I mentioned before ("[Flightgear-devel]
> Missing file in cvs for dhc2F") it is broken. My mail seems to have been
> ignored.
>
> R
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Melchior FRANZ wrote:
> * AnMaster -- Saturday 15 December 2007:
>> Yes but tar ball have been made [...]
>
> But they aren't released. Can still be fixed.
Indeed.
>
> I'd revert the last changes to the dhc2F that broke it.
> The manual seems to h
* AnMaster -- Saturday 15 December 2007:
> Yes but tar ball have been made [...]
But they aren't released. Can still be fixed.
I'd revert the last changes to the dhc2F that broke it.
The manual seems to have changed after the packaging, too,
and there certainly was a reason for the changes.
Let'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Yes but tar ball have been made while blocker bugs still existed. If we had a
real bug tracker this could have been avoided. Durk Talsma would have seen that
there was a bug marked as blocker then and could have waited until it was fixed.
But as it i
* AnMaster -- Saturday 15 December 2007:
> IIRC the Beaver was included. But as I mentioned before
> ("[Flightgear-devel] Missing file in cvs for dhc2F") it is
> broken. My mail seems to have been ignored.
That's bad, indeed. The whole aircraft should get thrown out.
There's a file in the seahawk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
IIRC the Beaver was included. But as I mentioned before ("[Flightgear-devel]
Missing file in cvs for dhc2F") it is broken. My mail seems to have been
ignored.
Regards,
Arvid Norlander
Durk Talsma wrote:
> Hi all,
>
> I just finished creating the
Hi all,
I just finished creating the release and placed the tar files on my server.
Due to the capacity limitations of my own server, I'm not providing a
download link here. They will hopefully shortly be transfered to the mirrors,
shortly. I've also given the people involved in building the wi
13 matches
Mail list logo
