Re: [E-devel] {Spam?} Re: {Spam?} Re: evas common engine as a direct rendering library?

2007-07-25 Thread Vincent Torri
On Wed, 25 Jul 2007, Carsten Haitzler (The Rasterman) wrote: be careful - then you need to deal with merging the branch - the existing software enigne code wont stay still forever. before talking about merging, maybe it's time to write some code. There has been several times, by mails,

Re: [E-devel] {Spam?} Re: {Spam?} Re: evas common engine as a direct rendering library?

2007-07-25 Thread The Rasterman
On Wed, 25 Jul 2007 16:01:05 +0200 (CEST) Vincent Torri [EMAIL PROTECTED] babbled: On Wed, 25 Jul 2007, Carsten Haitzler (The Rasterman) wrote: be careful - then you need to deal with merging the branch - the existing software enigne code wont stay still forever. before talking

Re: [E-devel] {Spam?} Re: {Spam?} Re: evas common engine as a direct rendering library?

2007-07-25 Thread Jorge Luis Zapata Muga
On 7/25/07, Vincent Torri [EMAIL PROTECTED] wrote: On Wed, 25 Jul 2007, Carsten Haitzler (The Rasterman) wrote: be careful - then you need to deal with merging the branch - the existing software enigne code wont stay still forever. before talking about merging, maybe it's time to write

Re: [E-devel] {Spam?} Re: {Spam?} Re: evas common engine as a direct rendering library?

2007-07-25 Thread Gustavo Sverzut Barbieri
On 7/25/07, Jorge Luis Zapata Muga [EMAIL PROTECTED] wrote: On 7/25/07, Vincent Torri [EMAIL PROTECTED] wrote: On Wed, 25 Jul 2007, Carsten Haitzler (The Rasterman) wrote: be careful - then you need to deal with merging the branch - the existing software enigne code wont stay still