nanogui: #if FOO vs. #ifdef BAR


Previous by date: 3 Jun 2005 20:54:13 +0100 Re: What's the difference between microwindows API and nano-X API, Alain Volmat
Next by date: 3 Jun 2005 20:54:13 +0100 Nano-X development tree, Alain Volmat
Previous in thread: 3 Jun 2005 20:54:13 +0100 Re: #if FOO vs. #ifdef BAR, Alain Volmat
Next in thread: 3 Jun 2005 20:54:13 +0100 Re: #if FOO vs. #ifdef BAR, Greg Haerr

Subject: Re: [nanogui] #if FOO vs. #ifdef BAR
From: Alexander Neundorf ####@####.####
Date: 3 Jun 2005 20:54:13 +0100
Message-Id: <200506032153.57300.neundorf@kde.org>

Hi,

On Thursday 02 June 2005 15:33, Alain Volmat wrote:
> The thing is that I'm not the guy who has permission of the CVS :D
>
> One solution (some guys already mentioned that recently on the ML)
> would be have a development tree. In a sense, this would be useful
> since it is better to properly test modifications BEFORE commiting
> them into the CVS (Greg insists on testing modifications with all
> configurations of screen type for example ... well it makes sences).
>
> The thing is that nanoX isn't a that big project and I'm not sure
> that such tree (like the mm tree of the linux kernel) is really necessary.
> Moreover it might even make maintenance work harder.
>
> What's other guys opinion ?

IMO an experimental branch/tree would be a good idea. There stuff can be added 
more easily and can be tested by more developers/users.

Bye
Alex
-- 
Work: ####@####.#### - http://www.jenoptik-los.de
Home: ####@####.####                - http://www.kde.org
      ####@####.####               - http://www.neundorf.net

Previous by date: 3 Jun 2005 20:54:13 +0100 Re: What's the difference between microwindows API and nano-X API, Alain Volmat
Next by date: 3 Jun 2005 20:54:13 +0100 Nano-X development tree, Alain Volmat
Previous in thread: 3 Jun 2005 20:54:13 +0100 Re: #if FOO vs. #ifdef BAR, Alain Volmat
Next in thread: 3 Jun 2005 20:54:13 +0100 Re: #if FOO vs. #ifdef BAR, Greg Haerr


Powered by ezmlm-browse 0.20.