1 Return-Path: <wael.nasreddine@gmail.com>
\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 olra.theworths.org (Postfix) with ESMTP id 27362431FBC
\r
6 for <notmuch@notmuchmail.org>; Thu, 15 May 2014 13:01:02 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
\r
13 FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id QYeoqS2Fcs0S for <notmuch@notmuchmail.org>;
\r
17 Thu, 15 May 2014 13:00:54 -0700 (PDT)
\r
18 Received: from mail-pb0-f48.google.com (mail-pb0-f48.google.com
\r
19 [209.85.160.48]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id 559DE431FAE
\r
22 for <notmuch@notmuchmail.org>; Thu, 15 May 2014 13:00:54 -0700 (PDT)
\r
23 Received: by mail-pb0-f48.google.com with SMTP id rr13so1516866pbb.7
\r
24 for <notmuch@notmuchmail.org>; Thu, 15 May 2014 13:00:53 -0700 (PDT)
\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
\r
26 h=from:to:cc:subject:in-reply-to:references:user-agent:date
\r
27 :message-id:mime-version:content-type;
\r
28 bh=9Nb2E3vcKnn7W+QUm//NtpE8f49sbD6mCC6RI38FP/c=;
\r
29 b=NQ+Oz3+QRtWnfG7bpVhtod80QsiyfyJyJKhjLedtoXXAvUBFQqFLZWlALRYU/aoASM
\r
30 BvIXUS3fCK50XziUU5MWw//mh4iNfMzZ/+RylrneK9tBNMtd2+6IPNnyuEhvml812/qw
\r
31 KNNDfdBTVtcWwGFCkCLdBV3E8jhlv6BLt3YspN72MLjEqINFcWBQQB/LeYWUN2Wj28ix
\r
32 RTOQZbrjPDeL9vsRJZwZnNvo6VyspMYdrYLzN+rZl65H8aH0uDjbG8opeyu7pcx6H9Ly
\r
33 zWyHt8e/LFaulLvbo7tAO01ejTp7IHjpizCX1pmtbk/tuA3fzm+Ui8ZBdnnKV/s6EvXb
\r
35 X-Received: by 10.68.193.100 with SMTP id hn4mr15072421pbc.50.1400184053447;
\r
36 Thu, 15 May 2014 13:00:53 -0700 (PDT)
\r
37 Received: from localhost ([2620:0:1000:2e00:69cd:3af5:6fe9:9efd])
\r
38 by mx.google.com with ESMTPSA id
\r
39 or4sm10575352pbb.17.2014.05.15.13.00.52 for <multiple recipients>
\r
40 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
\r
41 Thu, 15 May 2014 13:00:52 -0700 (PDT)
\r
42 From: Wael Nasreddine <wael.nasreddine@gmail.com>
\r
43 To: "W. Trevor King" <wking@tremily.us>
\r
44 Subject: Re: [PATCH v2] Enable Travis-CI as a backup continuous integration
\r
46 In-Reply-To: <20140515190445.GS11834@odin.tremily.us>
\r
47 References: <1400108004-26955-1-git-send-email-wael.nasreddine@gmail.com>
\r
48 <1400108004-26955-2-git-send-email-wael.nasreddine@gmail.com>
\r
49 <cun1tvv5zi3.fsf@hotblack-desiato.hh.sledj.net>
\r
50 <w52c8uq3szyh.fsf@gaea.mtv.corp.google.com>
\r
51 <20140515190445.GS11834@odin.tremily.us>
\r
52 User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.3.1
\r
53 (x86_64-pc-linux-gnu)
\r
54 Date: Thu, 15 May 2014 13:00:46 -0700
\r
55 Message-ID: <w52c61l6u80h.fsf@gaea.mtv.corp.google.com>
\r
57 Content-Type: multipart/mixed; boundary="=-=-="
\r
58 Cc: notmuch@notmuchmail.org
\r
59 X-BeenThere: notmuch@notmuchmail.org
\r
60 X-Mailman-Version: 2.1.13
\r
62 List-Id: "Use and development of the notmuch mail system."
\r
63 <notmuch.notmuchmail.org>
\r
64 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
65 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
66 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
67 List-Post: <mailto:notmuch@notmuchmail.org>
\r
68 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
69 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
70 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
71 X-List-Received-Date: Thu, 15 May 2014 20:01:02 -0000
\r
74 Content-Type: text/plain
\r
76 "W. Trevor King" <wking@tremily.us> writes:
\r
78 > On Thu, May 15, 2014 at 10:40:06AM -0700, Wael Nasreddine wrote:
\r
79 >> David Edmondson writes:
\r
80 >> > I realise that you might answer "I will keep this up to date", but
\r
81 >> > we have to worry about what happens if you lose interest and
\r
84 >> Absolutely, I understand your point and no one can guarantee
\r
85 >> maintainer-ship. I can modify my patch and add documentation
\r
86 >> (comments in the yaml file) about what each flag does, where can you
\r
87 >> documentation about it and of course details about the hack. Would
\r
90 > I personally love comments like this, but I prefer them in the commit
\r
91 > message. Otherwise the source becomes one humongous comment with a
\r
92 > bit of interspersed code ;). An interactive blame (like you get with
\r
93 > tig [1] and probably any interactive Git frontent) makes these
\r
94 > commit-messages easily accessible (assuming they're not buried under
\r
95 > whitespace churn, etc.)
\r
98 @Dan what do you think? File comments or commit message?
\r
103 > [1]: http://jonas.nitro.dk/tig/
\r
106 > This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
\r
107 > For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
\r
110 Content-Type: multipart/signed; boundary="==-=-=";
\r
111 micalg=pgp-sha1; protocol="application/pgp-signature"
\r
114 Content-Type: text/plain
\r
115 Content-Transfer-Encoding: quoted-printable
\r
118 Wael Nasreddine | SRE at Google | wael.nasreddine@gmail.com | (650) 735-1773
\r
121 Content-Type: application/pgp-signature
\r
123 -----BEGIN PGP SIGNATURE-----
\r
126 iEYEARECAAYFAlN1HO8ACgkQVWU5RcjdGKIzkgCg27eZVk8ytXaTJubTJw9TAPBm
\r
127 XO0An3dlzSQMmPS69r/4t97e/uux5ayG
\r
129 -----END PGP SIGNATURE-----
\r