On Fr, 2006-10-20 at 02:11 +0200, Øystein Gisnås wrote:
> > Øystein, can you make sure that it gets included in Debian packages
> if
> > Etch would otherwise be released with an E-D-S where this bug is
> still
> > present? Should I file a bug in the Debian tracker as a reminder?
>
> Yes and yes. I
On Mi, 2006-10-18 at 19:24 +0200, Patrick Ohly wrote:
> I found out what the problem is, see
> http://bugzilla.gnome.org/show_bug.cgi?id=363102
[...]
> There is a mutex, but none of the CORBA implementation functions lock
> it. Any suggestions how to fix this? As I said in that issue, several
> sol
2006/10/19, Patrick Ohly <[EMAIL PROTECTED]>:
> On So, 2006-10-15 at 22:57 +0200, Patrick Ohly wrote:
> > * Is someone going to take care of the reported regression or do
> > you need a patch to fix it? Whoever changed the code between 2.6
> > and 2.8 should be in a better pos
On So, 2006-10-15 at 22:57 +0200, Patrick Ohly wrote:
> * Is someone going to take care of the reported regression or do
> you need a patch to fix it? Whoever changed the code between 2.6
> and 2.8 should be in a better position to fix it, so I am a bit
> reluctant to
On Mo, 2006-10-16 at 19:21 +0200, Patrick Ohly wrote:
> > > * Is someone running Evolution and in particular the
> Evolution
> > > data server under valgrind as part of release testing or
> regular
> > > quality assurance?
> >
> > I know there is performance work in relation
On Sun, 2006-10-15 at 22:57 +0200, Patrick Ohly wrote:
> I have not mentioned it on this list before, so before I come to the
> real reason for this email let me introduce it briefly: SyncEvolution[1]
> is a SyncML client that I wrote to synchronize address books, calendars
> and tasks list betwee
On Sun, 2006-10-15 at 23:32 +0200, Øystein Gisnås wrote:
> 2006/10/15, Patrick Ohly <[EMAIL PROTECTED]>:
> > * Is someone going to take care of the reported regression or do
> > you need a patch to fix it? Whoever changed the code between 2.6
> > and 2.8 should be in a better
2006/10/15, Patrick Ohly <[EMAIL PROTECTED]>:
> * Is someone going to take care of the reported regression or do
> you need a patch to fix it? Whoever changed the code between 2.6
> and 2.8 should be in a better position to fix it, so I am a bit
> reluctant to investig
Hi all,
I have not mentioned it on this list before, so before I come to the
real reason for this email let me introduce it briefly: SyncEvolution[1]
is a SyncML client that I wrote to synchronize address books, calendars
and tasks list between Evolution and mobile devices or Evolution
instances o
