Le vendredi 04 mars 2011 à 05:47 -0700, Sankar P a écrit :
> > I'm working on "Enterprise" use of Evolution, and one of the big
> > requirements is encryption of data at rest. The answer "just encrypt the
> > whole of the user's home directory" only puts them off for so long.
> >
> > So I'm lookin
For 3.1, I would like to provide a top-level header file for each of the
libraries in E-D-S and deprecate including individual header files. The
benefits should be clear by now: more flexibility to change or rearrange
header files without breaking the public API.
Valid #include directives for E-D
On Fri, 2011-03-18 at 13:10 -0400, Matthew Barnes wrote:
> Would anyone object if I collect it all together under a top-level
> "tests" directory? (After we branch next week, of course.) This would
> include the automated unit tests for libebook and libecal as well as the
> standalone widget dem
Hi,
The meeting goes as follows,
* Project updates
* Discussion on queries/decisions
* Individual updates
Check out http://live.gnome.org/Evolution/CommunityMeet for more details.
- Chenthill.
___
evolution-hackers mailing list
evolution-hackers@gnome
will try to attend
> - Original message -
> From: "Chenthill Palanisamy"
> To: evolution-hackers@gnome.org
> Subject: [Evolution-hackers] [Reminder] Evolution community meeting at
> #evolution-meet channel - Mar 23 - 3:30 PM UTC
> Date: Wed, 23 Mar 2011 02:05:22 +0530
>
>
>Hi,
>
On Tue, 2011-03-22 at 14:35 -0400, Matthew Barnes wrote:
> For 3.1, I would like to provide a top-level header file for each of the
> libraries in E-D-S and deprecate including individual header files. The
> benefits should be clear by now: more flexibility to change or rearrange
> header files wi
