On Fri, 2011-05-06 at 10:01 +0200, sean finney wrote:
Hi Milan,
On Fri, May 06, 2011 at 08:56:10AM +0200, Milan Crha wrote:
As I already said seanus on irc, I will be evaluating the performance
between having vcards as files Vs having it in db and then choose the
one which would be
On Fri, 2011-05-06 at 08:56 +0200, Milan Crha wrote:
(Please do not reply to me, reply to the list, I read the list and I
prefer to Ctrl+L while your message avoids this feature for me. Thanks
for your understanding.)
On Thu, 2011-05-05 at 12:23 +0530, Chenthill wrote:
you scary me. Could
On Wed, 2011-05-04 at 14:37 +0200, Milan Crha wrote:
So here left basically three things,
a) merging some API in utils,
b) getting well-known properties,
c) setting well-known properties
Hi,
I just did a commit into the eclient branch with a fix for b) and c).
There is a
On Mo, 2011-05-09 at 17:00 +0200, Milan Crha wrote:
On Wed, 2011-05-04 at 14:37 +0200, Milan Crha wrote:
So here left basically three things,
a) merging some API in utils,
b) getting well-known properties,
c) setting well-known properties
Hi,
I just did a commit into
On Mon, 2011-05-09 at 17:41 +0200, Patrick Ohly wrote:
Why duplicate the LOADED/ONLINE/READONLY/CACHE_DIR/CAPABILITIES
properties? They could be defined as common E_CLIENT_BACKEND_
properties.
It's just because of (so called) consistency. With merging common error
codes into E_CLIENT_ERROR_
On Mon, 2011-05-09 at 17:49 +0200, Milan Crha wrote:
It's just because of (so called) consistency. With merging common error
codes into E_CLIENT_ERROR_ namespace I realized that checking for
particular errors will not be that easy as is now, because one might
have two switches, one for domain
