1 Return-Path: <tomi.ollila@iki.fi>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by arlo.cworth.org (Postfix) with ESMTP id 462E66DE1320
\r
6 for <notmuch@notmuchmail.org>; Sat, 21 Nov 2015 05:48:12 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at cworth.org
\r
11 X-Spam-Status: No, score=0.718 tagged_above=-999 required=5 tests=[AWL=0.066,
\r
12 SPF_NEUTRAL=0.652] autolearn=disabled
\r
13 Received: from arlo.cworth.org ([127.0.0.1])
\r
14 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id 5_ayaiv-9fZn for <notmuch@notmuchmail.org>;
\r
16 Sat, 21 Nov 2015 05:48:10 -0800 (PST)
\r
17 Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])
\r
18 by arlo.cworth.org (Postfix) with ESMTP id 024196DE0A87
\r
19 for <notmuch@notmuchmail.org>; Sat, 21 Nov 2015 05:48:09 -0800 (PST)
\r
20 Received: from guru.guru-group.fi (localhost [IPv6:::1])
\r
21 by guru.guru-group.fi (Postfix) with ESMTP id 11A6210007F;
\r
22 Sat, 21 Nov 2015 15:48:26 +0200 (EET)
\r
23 From: Tomi Ollila <tomi.ollila@iki.fi>
\r
24 To: Sam Halliday <sam.halliday@gmail.com>, notmuch@notmuchmail.org
\r
25 Subject: Re: github mirror
\r
26 In-Reply-To: <87bnvn111h.fsf@Samskara.home>
\r
27 References: <87bnvn111h.fsf@Samskara.home>
\r
28 User-Agent: Notmuch/0.21+26~g022a785 (http://notmuchmail.org) Emacs/24.3.1
\r
29 (x86_64-unknown-linux-gnu)
\r
30 X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL
\r
31 $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F
\r
32 !)g;OY^,BjTbr)Np:%c_o'jj,Z
\r
33 Date: Sat, 21 Nov 2015 15:48:25 +0200
\r
34 Message-ID: <m2mvu779au.fsf@guru.guru-group.fi>
\r
36 Content-Type: text/plain
\r
37 X-BeenThere: notmuch@notmuchmail.org
\r
38 X-Mailman-Version: 2.1.20
\r
40 List-Id: "Use and development of the notmuch mail system."
\r
41 <notmuch.notmuchmail.org>
\r
42 List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,
\r
43 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
44 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
\r
45 List-Post: <mailto:notmuch@notmuchmail.org>
\r
46 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
47 List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,
\r
48 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
49 X-List-Received-Date: Sat, 21 Nov 2015 13:48:12 -0000
\r
52 Exceptionally top-posting as the rest is left just for reference
\r
53 (for anyone interested and loosing the thread context)
\r
55 Marking this as notmuch::fixed as
\r
57 https://github.com/notmuch/notmuch
\r
59 fixes this and is usually up-to-date (I use this link on one of my
\r
60 notmuch installations)
\r
62 Interestingly the wiki is also in github (just that it is updated
\r
63 March 28 -- based on https://github.com/notmuch )
\r
69 On Sun, Apr 27 2014, Sam Halliday <sam.halliday@gmail.com> wrote:
\r
73 > I have just started using notmuch and I really love it! I've been using
\r
74 > web interfaces and proprietary mail clients for almost a decade and mutt
\r
75 > before that (because I never got on well with rmail or gnus). Now, I'm
\r
76 > trying to get all my life-hacker aficionados to follow suit.
\r
78 > I was wanting to submit an RFE for you and to browse your source code to
\r
79 > see how hard it would be to implement, but I was disappointed that it is
\r
80 > all hosted on your own git repository with no issue tracker.
\r
82 > While I appreciate that you probably use notmuch as your work flow
\r
83 > manager, it is also quite common to use a social website such as github
\r
84 > or getsatisfaction to interface with users. In my experience, github
\r
85 > dramatically increases the number of contributions from users, in the
\r
86 > form of what github calls "pull requests" (if you're a git user but not
\r
87 > a github user, the term is confusing).
\r
89 > Would it be possible to have a github project for notmuch? I'm certain
\r
90 > the git repositories could be synchronised easily.
\r
92 > A bridge between github's issue tracker and notmuch would be entirely
\r
93 > possible: they have an API that would allow addition and removal of
\r
94 > tags, as well as editing tickets. Actually, I would probably use such a
\r
97 > But in any case, my RFE/question was this: how hard would it be to have
\r
98 > an optional mode of behaviour where tags are stored in the message
\r
99 > itself, so that syncing with an IMAP server (e.g. via offlineimap)
\r
100 > would make the tags available on all devices. This would negate the need
\r
101 > for workarounds, such as shared notmuch databases, when users have
\r
102 > multiple machines.
\r
104 > It would also allow applications like offlineimap to introduce a gmail
\r
105 > plugin that would copy the message into a folder according to its tags,
\r
106 > so gmail labels and notmuch tags would be in sync.
\r
111 > _______________________________________________
\r
112 > notmuch mailing list
\r
113 > notmuch@notmuchmail.org
\r
114 > http://notmuchmail.org/mailman/listinfo/notmuch
\r