Re: [PATCH 2/9] Add a lazily-initialized crypto context to notmuch_database_t

2015-12-11 Thread Tomi Ollila
On Thu, Dec 10 2015, Daniel Kahn Gillmor wrote: > This is in large part a duplicate of parts of crypto.c, but that code > is in the client (outside the library), and we don't want to entangle > the libgmime API with the libnotmuch API. > > I welcome better proposals for how to share this code exp

Re: [PATCH 2/9] Add a lazily-initialized crypto context to notmuch_database_t

2015-12-11 Thread Daniel Kahn Gillmor
On Fri 2015-12-11 09:03:05 -0500, David Bremner wrote: > Daniel Kahn Gillmor writes: > >> This is in large part a duplicate of parts of crypto.c, but that code >> is in the client (outside the library), and we don't want to entangle >> the libgmime API with the libnotmuch API. >> >> I welcome bett

Re: [PATCH 2/9] Add a lazily-initialized crypto context to notmuch_database_t

2015-12-11 Thread David Bremner
Daniel Kahn Gillmor writes: > This is in large part a duplicate of parts of crypto.c, but that code > is in the client (outside the library), and we don't want to entangle > the libgmime API with the libnotmuch API. > > I welcome better proposals for how to share this code explicitly > between th

[PATCH 2/9] Add a lazily-initialized crypto context to notmuch_database_t

2015-12-09 Thread Daniel Kahn Gillmor
This is in large part a duplicate of parts of crypto.c, but that code is in the client (outside the library), and we don't want to entangle the libgmime API with the libnotmuch API. I welcome better proposals for how to share this code explicitly between the library and the client. --- lib/databa