Hi Matthew,
Am Montag 17 Oktober 2011, um 23:48:01 schrieb Matthew Barnes:
> On Mon, 2011-10-17 at 15:21 +0200, Christian Hilberg wrote:
> > Fair enough, thanks for clarifying. If that's the current status, then
> > nothing is lost if we keep the implementation as-is for now and try it
> > again
Hi,
The meeting goes as follows,
* Project updates
* Discussion on queries/decisions
* Individual updates
http://live.gnome.org/Evolution/CommunityMeet
- Chenthill.
___
evolution-hackers mailing list
evolution-hackers@gnome.org
To change your list
Hi Chen,
Am Dienstag 18 Oktober 2011, um 12:13:04 schrieb Chenthill:
> Hi,
> The meeting goes as follows,
> [...]
You sure the meeting is *today*, not tomorrow (i.e. Wednesday),
as usual? Just asking. :-)
(Bye)^2,
Christian
--
kernel concepts GbRTel: +49-271-771091-14
Siegh
On Tue, 2011-10-18 at 12:30 +0200, Christian Hilberg wrote:
> Hi Chen,
>
> Am Dienstag 18 Oktober 2011, um 12:13:04 schrieb Chenthill:
> > Hi,
> > The meeting goes as follows,
> > [...]
>
> You sure the meeting is *today*, not tomorrow (i.e. Wednesday),
> as usual? Just asking. :-)
Oh my bad, n
Here's a crazy idea...
What do you guys think about moving evolution-alarm-notify to E-D-S as a
simple D-Bus service? It could live in the new "services" directory:
evolution-data-server/services/evolution-alarm-notify/
evolution-alarm-notify is already an autostart program, launched when
y
On Tue, Oct 18, 2011 at 10:22 PM, Matthew Barnes wrote:
> Here's a crazy idea...
>
> What do you guys think about moving evolution-alarm-notify to E-D-S as a
> simple D-Bus service? It could live in the new "services" directory:
>
> evolution-data-server/services/evolution-alarm-notify/
>
> ev
On 18 October 2011 17:52, Matthew Barnes wrote:
> Here's a crazy idea...
>
> What do you guys think about moving evolution-alarm-notify to E-D-S as a
> simple D-Bus service? It could live in the new "services" directory:
>
> evolution-data-server/services/evolution-alarm-notify/
>
> evolution-
On Sat, 2011-10-15 at 11:18 -0400, Matthew Barnes wrote:
> Just a heads up that I've changed Camel's authentication API to factor
> out the password loop that each and every provider currently replicates
> for themselves. Turns out they all have the same basic logic flow.
Hi,
I'm currentl
On Tue, 2011-10-18 at 21:29 +0200, Milan Crha wrote:
> I'm currently trying to adapt evo-ews to current git master and this
> change doesn't make much sense there, at least for me, because on the
> first look there is used a libsoup for authentications, thus no such
> auth_loop or any "same basic
On Tue, 2011-10-18 at 15:58 -0400, Matthew Barnes wrote:
> On Tue, 2011-10-18 at 21:29 +0200, Milan Crha wrote:
> > I'm currently trying to adapt evo-ews to current git master and this
> > change doesn't make much sense there, at least for me, because on the
> > first look there is used a libsoup
Hi,
I cannot find the thread where this was discussed, I'm sorry, but after
few days I found why this behaviour is pretty bad and why the
evolution-alarm-notify didn't ask for passwords. My usecase is pretty
simple, and I believe there are many corporate users with the same
environment: I h
11 matches
Mail list logo
