unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Justus Winter <4winter@informatik.uni-hamburg.de>,
	Jameson Graef Rollins <jrollins@finestructure.net>,
	Felipe Contreras <felipe.contreras@gmail.com>
Cc: Ali Polatel <alip@exherbo.org>, notmuch@notmuchmail.org
Subject: Re: Can't compile notmuch-delivery
Date: Fri, 01 Jun 2012 23:14:35 -0300	[thread overview]
Message-ID: <87ehpyzchg.fsf@zancas.localnet> (raw)
In-Reply-To: <20120601224909.24629.70500@thinkbox.jade-hamburg.de>

Justus Winter <4winter@informatik.uni-hamburg.de> writes:

>
> I like the idea. The thing with the python bindings is that building
> them wont detect any errors, one has to import the module. Quick and
> dirty python oneliner that doesn't even require installing the
> bindings:

I guess the tests alreedy do at least this much for the python bindings
right?  I think that suffices; I never push without running the tests
first, and the release process automatically runs them. So I think
you're done, as far as minimal sanity checking of the python bindings
goes.

d

  reply	other threads:[~2012-06-02  2:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 21:42 Can't compile notmuch-delivery Jostein Gogstad
2012-06-01  6:44 ` Tomi Ollila
2012-06-01  8:54   ` Felipe Contreras
2012-06-01 13:43     ` David Bremner
2012-06-01 17:01       ` Jameson Graef Rollins
2012-06-01 18:17         ` David Bremner
2012-06-01 18:28           ` Jameson Graef Rollins
2012-06-01 18:46             ` David Bremner
2012-06-01 22:49               ` Justus Winter
2012-06-02  2:14                 ` David Bremner [this message]
2012-06-01 18:44           ` Felipe Contreras
2012-06-03  5:35         ` Adam Wolfe Gordon
2012-06-04  7:02   ` Jostein Gogstad
2012-06-04  7:07     ` Jostein Gogstad

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ehpyzchg.fsf@zancas.localnet \
    --to=david@tethera.net \
    --cc=4winter@informatik.uni-hamburg.de \
    --cc=alip@exherbo.org \
    --cc=felipe.contreras@gmail.com \
    --cc=jrollins@finestructure.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).