Return-Path: <wael.nasreddine@gmail.com>
X-Original-To: notmuch@notmuchmail.org
Delivered-To: notmuch@notmuchmail.org
Received: from localhost (localhost [127.0.0.1])
	by olra.theworths.org (Postfix) with ESMTP id 27362431FBC
	for <notmuch@notmuchmail.org>; Thu, 15 May 2014 13:01:02 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level: 
X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5
	tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
	FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
Received: from olra.theworths.org ([127.0.0.1])
	by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id QYeoqS2Fcs0S for <notmuch@notmuchmail.org>;
	Thu, 15 May 2014 13:00:54 -0700 (PDT)
Received: from mail-pb0-f48.google.com (mail-pb0-f48.google.com
	[209.85.160.48]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by olra.theworths.org (Postfix) with ESMTPS id 559DE431FAE
	for <notmuch@notmuchmail.org>; Thu, 15 May 2014 13:00:54 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id rr13so1516866pbb.7
	for <notmuch@notmuchmail.org>; Thu, 15 May 2014 13:00:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=from:to:cc:subject:in-reply-to:references:user-agent:date
	:message-id:mime-version:content-type;
	bh=9Nb2E3vcKnn7W+QUm//NtpE8f49sbD6mCC6RI38FP/c=;
	b=NQ+Oz3+QRtWnfG7bpVhtod80QsiyfyJyJKhjLedtoXXAvUBFQqFLZWlALRYU/aoASM
	BvIXUS3fCK50XziUU5MWw//mh4iNfMzZ/+RylrneK9tBNMtd2+6IPNnyuEhvml812/qw
	KNNDfdBTVtcWwGFCkCLdBV3E8jhlv6BLt3YspN72MLjEqINFcWBQQB/LeYWUN2Wj28ix
	RTOQZbrjPDeL9vsRJZwZnNvo6VyspMYdrYLzN+rZl65H8aH0uDjbG8opeyu7pcx6H9Ly
	zWyHt8e/LFaulLvbo7tAO01ejTp7IHjpizCX1pmtbk/tuA3fzm+Ui8ZBdnnKV/s6EvXb
	BJdg==
X-Received: by 10.68.193.100 with SMTP id hn4mr15072421pbc.50.1400184053447;
	Thu, 15 May 2014 13:00:53 -0700 (PDT)
Received: from localhost ([2620:0:1000:2e00:69cd:3af5:6fe9:9efd])
	by mx.google.com with ESMTPSA id
	or4sm10575352pbb.17.2014.05.15.13.00.52 for <multiple recipients>
	(version=TLSv1.2 cipher=RC4-SHA bits=128/128);
	Thu, 15 May 2014 13:00:52 -0700 (PDT)
From: Wael Nasreddine <wael.nasreddine@gmail.com>
To: "W. Trevor King" <wking@tremily.us>
Subject: Re: [PATCH v2] Enable Travis-CI as a backup continuous integration
	service.
In-Reply-To: <20140515190445.GS11834@odin.tremily.us>
References: <1400108004-26955-1-git-send-email-wael.nasreddine@gmail.com>
	<1400108004-26955-2-git-send-email-wael.nasreddine@gmail.com>
	<cun1tvv5zi3.fsf@hotblack-desiato.hh.sledj.net>
	<w52c8uq3szyh.fsf@gaea.mtv.corp.google.com>
	<20140515190445.GS11834@odin.tremily.us>
User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.3.1
	(x86_64-pc-linux-gnu)
Date: Thu, 15 May 2014 13:00:46 -0700
Message-ID: <w52c61l6u80h.fsf@gaea.mtv.corp.google.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
Cc: notmuch@notmuchmail.org
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Use and development of the notmuch mail system."
	<notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Thu, 15 May 2014 20:01:02 -0000

--=-=-=
Content-Type: text/plain

"W. Trevor King" <wking@tremily.us> writes:

> On Thu, May 15, 2014 at 10:40:06AM -0700, Wael Nasreddine wrote:
>> David Edmondson writes:
>> > I realise that you might answer "I will keep this up to date", but
>> > we have to worry about what happens if you lose interest and
>> > wander away.
>> 
>> Absolutely, I understand your point and no one can guarantee
>> maintainer-ship. I can modify my patch and add documentation
>> (comments in the yaml file) about what each flag does, where can you
>> documentation about it and of course details about the hack. Would
>> that be helpful?
>
> I personally love comments like this, but I prefer them in the commit
> message.  Otherwise the source becomes one humongous comment with a
> bit of interspersed code ;).  An interactive blame (like you get with
> tig [1] and probably any interactive Git frontent) makes these
> commit-messages easily accessible (assuming they're not buried under
> whitespace churn, etc.)
>

@Dan what do you think? File comments or commit message?

> Cheers,
> Trevor
>
> [1]: http://jonas.nitro.dk/tig/
>
> -- 
> This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
> For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

--=-=-=
Content-Type: multipart/signed; boundary="==-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"

--==-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

=2D-=20
Wael Nasreddine | SRE at Google | wael.nasreddine@gmail.com | (650) 735-1773

--==-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlN1HO8ACgkQVWU5RcjdGKIzkgCg27eZVk8ytXaTJubTJw9TAPBm
XO0An3dlzSQMmPS69r/4t97e/uux5ayG
=BNIS
-----END PGP SIGNATURE-----
--==-=-=--

--=-=-=--