On Fri, 20 Jan 2012 00:52:47 +0100, Thomas Jost
wrote:
>
> Here is how I did:
>
> (ldd notmuch | grep -q gmime-2.6) && test_subtest_known_broken
>
> ldd notmuch will show "/path/to/libgmime-2.4.so.*" or
> "libgmime-2.6.so.*" so we can easily check this in the test suite.
> It's a little
On Tue, 17 Jan 2012 15:38:36 -0500, Austin Clements wrote:
> Quoth Thomas Jost on Jan 17 at 11:48 am:
> > On Mon, 16 Jan 2012 22:47:14 -0500, Austin Clements
> > wrote:
> > > Quoth Thomas Jost on Jan 17 at 12:56 am:
> > > > This is mostly based on id:"8762i8hrb9.fsf at
On Fri, 20 Jan 2012 00:52:47 +0100, Thomas Jost schno...@schnouki.net wrote:
Here is how I did:
(ldd notmuch | grep -q gmime-2.6) test_subtest_known_broken
ldd notmuch will show /path/to/libgmime-2.4.so.* or
libgmime-2.6.so.* so we can easily check this in the test suite.
It's a
On Tue, 17 Jan 2012 15:38:36 -0500, Austin Clements amdra...@mit.edu wrote:
Quoth Thomas Jost on Jan 17 at 11:48 am:
On Mon, 16 Jan 2012 22:47:14 -0500, Austin Clements amdra...@mit.edu
wrote:
Quoth Thomas Jost on Jan 17 at 12:56 am:
This is mostly based on
Quoth Thomas Jost on Jan 17 at 11:48 am:
> On Mon, 16 Jan 2012 22:47:14 -0500, Austin Clements
> wrote:
> > Quoth Thomas Jost on Jan 17 at 12:56 am:
> > > This is mostly based on id:"8762i8hrb9.fsf at bookbinder.fernseed.info".
> > >
> > > This was tested against both gmime 2.6.4 and 2.4.31.
Hi,
Just a couple of comments inline :)
On Mon, 16 Jan 2012 22:47:14 -0500, Austin Clements wrote:
> Quoth Thomas Jost on Jan 17 at 12:56 am:
> > There are lots of API changes in gmime 2.6 crypto handling. By adding
> > preprocessor directives, it is however possible to add gmime 2.6
> >
Hi,
On Tue, 17 Jan 2012 00:56:39 +0100, Thomas Jost
wrote:
> There are lots of API changes in gmime 2.6 crypto handling. By adding
> preprocessor directives, it is however possible to add gmime 2.6 compatibility
> while preserving compatibility with gmime 2.4 too.
This approach is better
On Mon, 16 Jan 2012 22:47:14 -0500, Austin Clements wrote:
> Quoth Thomas Jost on Jan 17 at 12:56 am:
> > There are lots of API changes in gmime 2.6 crypto handling. By adding
> > preprocessor directives, it is however possible to add gmime 2.6
> > compatibility
> > while preserving
Thomas Jost(schnouki at schnouki.net)@170112-00:56:
> There are lots of API changes in gmime 2.6 crypto handling. By adding
> preprocessor directives, it is however possible to add gmime 2.6 compatibility
> while preserving compatibility with gmime 2.4 too.
>
> This is mostly based on
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
This is mostly based on id:"8762i8hrb9.fsf at bookbinder.fernseed.info".
This was tested against
On Mon, 16 Jan 2012 22:47:14 -0500, Austin Clements amdra...@mit.edu wrote:
Quoth Thomas Jost on Jan 17 at 12:56 am:
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6
compatibility
while preserving
Quoth Thomas Jost on Jan 17 at 11:48 am:
On Mon, 16 Jan 2012 22:47:14 -0500, Austin Clements amdra...@mit.edu wrote:
Quoth Thomas Jost on Jan 17 at 12:56 am:
This is mostly based on id:8762i8hrb9@bookbinder.fernseed.info.
This was tested against both gmime 2.6.4 and 2.4.31. With
On Tue, Jan 17, 2012 at 12:56:39AM +0100, Thomas Jost wrote:
> There are lots of API changes in gmime 2.6 crypto handling. By adding
> preprocessor directives, it is however possible to add gmime 2.6 compatibility
> while preserving compatibility with gmime 2.4 too.
I tested this with gmime
Quoth Thomas Jost on Jan 17 at 12:56 am:
> There are lots of API changes in gmime 2.6 crypto handling. By adding
> preprocessor directives, it is however possible to add gmime 2.6 compatibility
> while preserving compatibility with gmime 2.4 too.
Awesome. Comments inline below.
> This is mostly
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
This is mostly based on id:8762i8hrb9@bookbinder.fernseed.info.
This was tested against both
On Tue, Jan 17, 2012 at 12:56:39AM +0100, Thomas Jost wrote:
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
I tested this with gmime 2.4.31
Quoth Thomas Jost on Jan 17 at 12:56 am:
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
Awesome. Comments inline below.
This is mostly
17 matches
Mail list logo
