2010-August Archive by Thread

Messages are ordered newest-to-oldest in this index. The newest threads will be at the top of this page, the oldest will be at the bottom.

Within a single thread, the first mail note is the START of the thread; the notes following that are in the chronological order of when they were received. So globally, newest messages are at the top, but within a thread, the oldest (the start of the thread) is at the top.

If you think about it, it is confusing. Just go with the flow and everything will be all right.

  • [Evolution-hackers] evolution-kolab: IMAPX RFC2086/RFC4314 (IMAP4 ACL) compliance, Christian Hilberg
  • [Evolution-hackers] Specifications for kolab plugin development, Silvan Marco Fin
  • [Evolution-hackers] Memory leaks, David Woodhouse
  • [Evolution-hackers] Rewrite e_load_book_source_async(), Matthew Barnes
  • [Evolution-hackers] [Reminder] Evolution community meeting at #evolution-meet channel - July 18 - 3:30 PM UTC, chen
  • [Evolution-hackers] evolution-kolab: working with multiple Camel.Provider instances, Christian Hilberg
  • Re: [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?), Stef Walter
  • [Evolution-hackers] Evolution 2.28.3 - change default mail folder (continued), Joop Beekmans
  • [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?), Christian Hilberg
  • Re: [Evolution-hackers] Camel IMAPX RFC5464 compliance, Christian Hilberg

  • Mail converted by MHonArc