Re: [Evolution-hackers] Removing libical fork, moving to new upstream?

2008-09-10 Thread dothebart
>Mi Sep 10 2008 11:26:31 EDT von Chenthill in 00.Sent Items> an >Patrick Ohly >Betreff: Re: [Evolution-hackers] Removing libical fork, moving to new >upstream? > > >>> >>> > How would you feel about a global flag which tells libical how to >>> > allocate memory? >>> >>> The problem with t

Re: [Evolution-hackers] Removing libical fork, moving to new upstream?

2008-09-10 Thread Patrick Ohly
On Wed, 2008-09-10 at 08:18 -0400, dothebart wrote: > Since it doesn't make sense imho to mix old style and new style api > calls in one application imho, and I hink we can deprecate the old > style. We can deprecate it, but as you said yourself earlier, moving all developers over to the new API a

Re: [Evolution-hackers] Evolution: Taking forward...

2008-09-10 Thread Jiri Lebl
Hello, Apparently I've been told that I have some code in evolution, despite having no memory of it. Anyway, since I assume you guys know better than I do, I guess I do. So in that case, feel free to relicense any of my code as outlined below. George Srinivasa Ragavan wrote: Hello guys,

Re: [Evolution-hackers] Removing libical fork, moving to new upstream?

2008-09-10 Thread IGnatius T Foobar
Chenthill wrote: So it is better to inform all the stake holders about the change and let them depend on the library versions to decide whether to free the memory or not if they have a need to depend on the older versions of libical. I think no one deny to make the necessary changes knowing that