--- /dev/null
+Return-Path: <tomi.ollila@iki.fi>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 462E66DE1320\r
+ for <notmuch@notmuchmail.org>; Sat, 21 Nov 2015 05:48:12 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.718\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.718 tagged_above=-999 required=5 tests=[AWL=0.066, \r
+ SPF_NEUTRAL=0.652] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id 5_ayaiv-9fZn for <notmuch@notmuchmail.org>;\r
+ Sat, 21 Nov 2015 05:48:10 -0800 (PST)\r
+Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 024196DE0A87\r
+ for <notmuch@notmuchmail.org>; Sat, 21 Nov 2015 05:48:09 -0800 (PST)\r
+Received: from guru.guru-group.fi (localhost [IPv6:::1])\r
+ by guru.guru-group.fi (Postfix) with ESMTP id 11A6210007F;\r
+ Sat, 21 Nov 2015 15:48:26 +0200 (EET)\r
+From: Tomi Ollila <tomi.ollila@iki.fi>\r
+To: Sam Halliday <sam.halliday@gmail.com>, notmuch@notmuchmail.org\r
+Subject: Re: github mirror\r
+In-Reply-To: <87bnvn111h.fsf@Samskara.home>\r
+References: <87bnvn111h.fsf@Samskara.home>\r
+User-Agent: Notmuch/0.21+26~g022a785 (http://notmuchmail.org) Emacs/24.3.1\r
+ (x86_64-unknown-linux-gnu)\r
+X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL\r
+ $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F\r
+ !)g;OY^,BjTbr)Np:%c_o'jj,Z\r
+Date: Sat, 21 Nov 2015 15:48:25 +0200\r
+Message-ID: <m2mvu779au.fsf@guru.guru-group.fi>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://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: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 21 Nov 2015 13:48:12 -0000\r
+\r
+\r
+Exceptionally top-posting as the rest is left just for reference\r
+(for anyone interested and loosing the thread context)\r
+\r
+Marking this as notmuch::fixed as\r
+\r
+https://github.com/notmuch/notmuch\r
+\r
+fixes this and is usually up-to-date (I use this link on one of my\r
+notmuch installations)\r
+\r
+Interestingly the wiki is also in github (just that it is updated\r
+March 28 -- based on https://github.com/notmuch )\r
+\r
+\r
+Tomi\r
+\r
+\r
+On Sun, Apr 27 2014, Sam Halliday <sam.halliday@gmail.com> wrote:\r
+\r
+> Dear NotMuch,\r
+>\r
+> I have just started using notmuch and I really love it! I've been using\r
+> web interfaces and proprietary mail clients for almost a decade and mutt\r
+> before that (because I never got on well with rmail or gnus). Now, I'm\r
+> trying to get all my life-hacker aficionados to follow suit.\r
+>\r
+> I was wanting to submit an RFE for you and to browse your source code to\r
+> see how hard it would be to implement, but I was disappointed that it is\r
+> all hosted on your own git repository with no issue tracker.\r
+>\r
+> While I appreciate that you probably use notmuch as your work flow\r
+> manager, it is also quite common to use a social website such as github\r
+> or getsatisfaction to interface with users. In my experience, github\r
+> dramatically increases the number of contributions from users, in the\r
+> form of what github calls "pull requests" (if you're a git user but not\r
+> a github user, the term is confusing).\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
+> 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
+> But in any case, my RFE/question was this: how hard would it be to have\r
+> an optional mode of behaviour where tags are stored in the message\r
+> itself, so that syncing with an IMAP server (e.g. via offlineimap)\r
+> would make the tags available on all devices. This would negate the need\r
+> for workarounds, such as shared notmuch databases, when users have\r
+> multiple machines.\r
+>\r
+> It would also allow applications like offlineimap to introduce a gmail\r
+> plugin that would copy the message into a folder according to its tags,\r
+> so gmail labels and notmuch tags would be in sync.\r
+>\r
+> Best regards,\r
+> Sam\r
+>\r
+> _______________________________________________\r
+> notmuch mailing list\r
+> notmuch@notmuchmail.org\r
+> http://notmuchmail.org/mailman/listinfo/notmuch\r