Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[11022] branches/qt

2010-06-23 Thread Per Inge Mathisen
On Wed, Jun 23, 2010 at 5:03 AM, wrote: > Qt dies on this date, Tuesday, June 22, 2010. > R.I.P Is this supposed to be some kind of practical joke? - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev

Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[11022] branches/qt

2010-06-23 Thread Guangcong Luo
On Wed, Jun 23, 2010 at 2:10 AM, Per Inge Mathisen wrote: > On Wed, Jun 23, 2010 at 5:03 AM,   wrote: >> Qt dies on this date, Tuesday, June 22, 2010. >> R.I.P > > Is this supposed to be some kind of practical joke? It's not clear from the commit message (since the commit message is a joke), but

[warzone2100-dev] [Warzone 2100 Trac] #1939: Initial power amount in Gamma1 depending on how mission was started

2010-06-23 Thread Warzone 2100 Trac
#1939: Initial power amount in Gamma1 depending on how mission was started -+-- Reporter: Emdek |Type: bug Status: new |Priority: major Milest

Re: [warzone2100-dev] svn/2.3 feature locked status, and what should happen with it

2010-06-23 Thread Per Inge Mathisen
One thing we should consider backporting to 2.3 is the wavecast code, which makes visibility a ton faster in trunk than in 2.3. - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev

[warzone2100-dev] [Warzone 2100 Trac] #1940: Make asserts continuable (in gdb at least)

2010-06-23 Thread Warzone 2100 Trac
#1940: Make asserts continuable (in gdb at least) -+-- Reporter: cybersphinx | Owner: Type: patch| Status: new Priority: major| Milest

[warzone2100-dev] [Warzone 2100 Trac] #1941: #include is invalid

2010-06-23 Thread Warzone 2100 Trac
#1941: #include is invalid -+-- Reporter: ohnobi...@… |Type: bug Status: new |Priority: minor Milestone: unspecified

Re: [warzone2100-dev] svn/2.3 feature locked status, and what should happen with it

2010-06-23 Thread buginator
On 6/23/10, Per Inge Mathisen wrote: > One thing we should consider backporting to 2.3 is the wavecast code, > which makes visibility a ton faster in trunk than in 2.3. > Though, that doesn't answer the question on what we should do with the 2.3 branch. If we start to add features that do requir

Re: [warzone2100-dev] svn/2.3 feature locked status, and what should happen with it

2010-06-23 Thread Per Inge Mathisen
On Thu, Jun 24, 2010 at 5:40 AM, buginator wrote: > If we start to add features that do require beta testing, what are we > going to do ? We could do beta testing... - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinf