--- /dev/null
+Return-Path: <sam.halliday@gmail.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 1E2F7431FBD\r
+ for <notmuch@notmuchmail.org>; Sun, 27 Apr 2014 11:53:34 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 2.6\r
+X-Spam-Level: **\r
+X-Spam-Status: No, score=2.6 tagged_above=-999 required=5\r
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+ FREEMAIL_FROM=0.001, RCVD_ILLEGAL_IP=3.399, RCVD_IN_DNSWL_LOW=-0.7]\r
+ autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id NjxvyIQ6yn+m for <notmuch@notmuchmail.org>;\r
+ Sun, 27 Apr 2014 11:53:26 -0700 (PDT)\r
+Received: from mail-we0-f179.google.com (mail-we0-f179.google.com\r
+ [74.125.82.179]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id B4A27431FBC\r
+ for <notmuch@notmuchmail.org>; Sun, 27 Apr 2014 11:53:25 -0700 (PDT)\r
+Received: by mail-we0-f179.google.com with SMTP id x48so5582004wes.10\r
+ for <notmuch@notmuchmail.org>; Sun, 27 Apr 2014 11:53:22 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+ h=from:to:subject:user-agent:date:message-id:mime-version\r
+ :content-type; bh=gLI15lkW+YMj2etC+XrkK9EqfFvUUN9XP/bnRJEIDM8=;\r
+ b=KZELlBKKAxCCqprIw4pdaD8zUCvtURwcaSoe0J9+/QZ6vTBKgxguMrM9kztL9EajIz\r
+ h8ziI2aJT0Y8i3jFViU/CPeU3yJiznyWr8N1JTzMlSg9HkGEEcxV38I3B0HPmOomBvv+\r
+ EJYH1m8BceNFc0JU2xgv4J1crhYehWX9UYnaclIu7iCaZRDP0AVKfavbyltckB+KD/rk\r
+ RCGzrPkwECaFKwCKyoLeK5Dyn3k7CkZVhcE/ovFcW//hJJQ0nFX8MYQfRutbJn+N5LJo\r
+ gMNUlBLrcSgGWXUSBsrJT+QPhftV+7HHxQsrJceuWfqxtuud7ObnlAVxdf++IC2QmPqI\r
+ K0ig==\r
+X-Received: by 10.180.189.65 with SMTP id gg1mr12178432wic.56.1398624802148;\r
+ Sun, 27 Apr 2014 11:53:22 -0700 (PDT)\r
+Received: from Samskara.home (host5-81-31-114.range5-81.btcentralplus.com.\r
+ [5.81.31.114]) by mx.google.com with ESMTPSA id\r
+ km2sm22236586wjb.13.2014.04.27.11.53.15 for <notmuch@notmuchmail.org>\r
+ (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+ Sun, 27 Apr 2014 11:53:15 -0700 (PDT)\r
+From: Sam Halliday <sam.halliday@gmail.com>\r
+To: notmuch@notmuchmail.org\r
+Subject: [Sam Halliday] Re: github mirror\r
+User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.3.1\r
+ (x86_64-unknown-linux-gnu)\r
+Date: Sun, 27 Apr 2014 19:53:33 +0100\r
+Message-ID: <87mwf6txhu.fsf@Samskara.home>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/mixed; boundary="==-=-="\r
+X-Mailman-Approved-At: Sun, 27 Apr 2014 12:28:04 -0700\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sun, 27 Apr 2014 18:53:34 -0000\r
+\r
+--==-=-=\r
+Content-Type: text/plain\r
+\r
+Sorry, I replied to jani and not the list...\r
+\r
+\r
+--==-=-=\r
+Content-Type: message/rfc822\r
+Content-Disposition: inline\r
+Content-Transfer-Encoding: 8bit\r
+\r
+Return-Path: <sam.halliday@gmail.com>\r
+Received: from Samskara.home (host5-81-31-114.range5-81.btcentralplus.com.\r
+ [5.81.31.114]) by mx.google.com with ESMTPSA id\r
+ gc19sm12258278wic.5.2014.04.27.10.57.25 for <jani@nikula.org>\r
+ (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 27 Apr 2014\r
+ 10:57:25 -0700 (PDT)\r
+From: Sam Halliday <sam.halliday@gmail.com>\r
+To: Jani Nikula <jani@nikula.org>\r
+Subject: Re: github mirror\r
+In-Reply-To: <8761lu928m.fsf@nikula.org>\r
+References: <87bnvn111h.fsf@Samskara.home> <8761lu928m.fsf@nikula.org>\r
+User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.3.1\r
+ (x86_64-unknown-linux-gnu)\r
+Date: Sun, 27 Apr 2014 18:57:47 +0100\r
+Message-ID: <87sioyu02s.fsf@Samskara.home>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+ micalg=pgp-sha1; protocol="application/pgp-signature"\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+\r
+Jani Nikula <jani@nikula.org> writes:\r
+> We also maintain fairly high standards for the contributions we\r
+> accept, so the review has a significant role in the process.\r
+\r
+In my experience the github pull review process is by far superior to\r
+any other solution. If you've never done a github review, I would\r
+strongly recommend doing one just for fun to see what you think of\r
+it. You can basically add line comments in the code and have a\r
+discussion on the finer points of commits. And then, to address those\r
+comments, it's as simple as the contributor pushing to their repo again\r
+and the review is updated. Repeat until the "merge" button is pressed\r
+(or the equivalent git commands, of course).\r
+\r
+But you are correct, it would be a big change from your current\r
+setup.\r
+\r
+>> Would it be possible to have a github project for notmuch? I'm certain\r
+>> the git repositories could be synchronised easily.\r
+>\r
+> This part is trivial, but on its own it doesn't provide any obvious\r
+> benefits.\r
+\r
+The benefit would be - perhaps - an increase in the number of patches\r
+for you to review :-). Plus, free hosting, and easier to track down who\r
+aims to contribute to the project. It would also expose you to a larger\r
+audience. I find a lot of cool projects just by jumping around\r
+interesting developers on github.\r
+\r
+I can only cite my own experience, but I have received a lot more\r
+contributions (out of the blue) since moving to github than I did when I\r
+was running repositories on savannah, sourceforge or google code. It's\r
+just so much easier to click the "fork" button, then make some commits,\r
+and click the "pull request" button. If I were contributing to you, it\r
+requires having to learn your process, create diffs and then attach\r
+them, and then after a review it means tracking down the bits of the\r
+code you're referring to and manually reconciling that with my repo and\r
+sending you more diffs. Using github, it's like all open source\r
+developers agree on a basic set of common processes.\r
+\r
+\r
+>> A bridge between github's issue tracker and notmuch would be entirely\r
+>> possible: they have an API that would allow addition and removal of\r
+>> tags, as well as editing tickets. Actually, I would probably use such a\r
+>> thing :-)\r
+>\r
+> I'm sure all of this would be entirely possible; I'm not so sure it\r
+> would be worth the effort. But hey, if someone is willing to do the\r
+> work, patches are welcome. By email. ;)\r
+\r
+Heh, well I might just end up doing something like that because the more\r
+I use notmuch, the more I think it could be used for other parts of my\r
+workflow. For example, I wrote https://github.com/fommil/zibaldone a\r
+couple of years ago for a friend but I never quite got it to a stage\r
+where I would use it myself. If I could use notmuch to manage a large\r
+collection of notes, that would be interesting, and would mean I could\r
+drop to the zibaldone visual (auto-cluster) mode and use a touchscreen\r
+to move the ideas around and find new connections. I'm using Lucene in\r
+that project, but I could rewrite the backend to use notmuch (or xapian\r
+directly). There are a few tickets on that project I'd love to implement\r
+(on the machine learning side) but on their own are not convincing\r
+enough for me to start using it.\r
+\r
+That said, Zibaldone and note organisation is low priority. If I were to\r
+do anything with notmuch it would be improving syncing with gmail (so a\r
+tag in notmuch equates to a label in their interface) or at the very\r
+least sharing the same tag structure across multiple notmuch\r
+machines. Being able to see the same thing on multiple machines using\r
+one canonical data source is really important for me.\r
+\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.12 (GNU/Linux)\r
+\r
+iEYEARECAAYFAlNdRRsACgkQh5Q4qVL9G8l9cgCfRExczj9MnYktYpDdja+ErRfF\r
+grMAnjUxY0GaQ58fu7dZspCMBhMAoO2n\r
+=cmex\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r
+\r
+--==-=-=\r
+Content-Type: multipart/signed; boundary="===-=-=";\r
+ micalg=pgp-sha1; protocol="application/pgp-signature"\r
+\r
+--===-=-=\r
+Content-Type: text/plain\r
+\r
+\r
+--===-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.12 (GNU/Linux)\r
+\r
+iEYEARECAAYFAlNdUi0ACgkQh5Q4qVL9G8kAFQCbBML9n0EX+3TRkV+t+SzPZhcw\r
+hr0An1WfuwGvMVDM3d04NyL33pYBoVwP\r
+=fOxR\r
+-----END PGP SIGNATURE-----\r
+--===-=-=--\r
+\r
+--==-=-=--\r