Re: elisp + company completion patches, v7

diff --git a/93/da8325251e1e9998e656f24bf20a59658ea166 b/93/da8325251e1e9998e656f24bf20a59658ea166
new file mode 100644 (file)
index 0000000..a9bec1a
--- /dev/null
+++ b/93/da8325251e1e9998e656f24bf20a59658ea166
@@ -0,0 +1,102 @@
+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 E47626DE14D6\r
+ for <notmuch@notmuchmail.org>; Tue, 27 Oct 2015 15:55:34 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.746\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.746 tagged_above=-999 required=5 tests=[AWL=0.094, \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 owF80TKUMsci for <notmuch@notmuchmail.org>;\r
+ Tue, 27 Oct 2015 15:55:32 -0700 (PDT)\r
+Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 095656DE133A\r
+ for <notmuch@notmuchmail.org>; Tue, 27 Oct 2015 15:55:31 -0700 (PDT)\r
+Received: from guru.guru-group.fi (localhost [IPv6:::1])\r
+ by guru.guru-group.fi (Postfix) with ESMTP id 67127100046;\r
+ Wed, 28 Oct 2015 00:55:33 +0200 (EET)\r
+From: Tomi Ollila <tomi.ollila@iki.fi>\r
+To: Carl Worth <cworth@cworth.org>, David Bremner <david@tethera.net>,\r
+ notmuch@notmuchmail.org\r
+Subject: Re: elisp + company completion patches, v7\r
+In-Reply-To: <871tche9vr.fsf@wondoo.home.cworth.org>\r
+References: <1445786638-13763-1-git-send-email-david@tethera.net>\r
+ <m2lhaqu23j.fsf@guru.guru-group.fi> <871tche9vr.fsf@wondoo.home.cworth.org>\r
+User-Agent: Notmuch/0.21~rc3+7~g28030b0 (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: Wed, 28 Oct 2015 00:55:33 +0200\r
+Message-ID: <m2k2q7exay.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: Tue, 27 Oct 2015 22:55:35 -0000\r
+\r
+On Mon, Oct 26 2015, Carl Worth <cworth@cworth.org> wrote:\r
+\r
+> On Sun, Oct 25 2015, Tomi Ollila wrote:\r
+>> I, if this does not sound nitpicking, would amend those 'This patch' and\r
+>> 'With this patch' texts in commit messages away by some rewording -- those\r
+>> pose as a bad example for someone reading the code -- and diminish the\r
+>> effect when I complain that again in future patched ;)\r
+>\r
+> What's the motivation here?\r
+>\r
+> It's often the case that a good commit message needs to describe the way\r
+> things were working prior to a commit, (describing the bug or missing\r
+> feature or what have you), and also needs to describe the change that is\r
+> affected by the commit itself.\r
+>\r
+> So I actually like seeing commit messages that say things like:\r
+>\r
+>     Prior to this commit... (some bug existed...)\r
+>\r
+>     In this commit... (some code is reworked to fix the bug...)\r
+>\r
+> But maybe I've missed the point of your message.\r
+>\r
+>\r
+> -Carl\r
+\r
+Probably the missing point is the fine distinction between \r
+'this patch' and 'this commit'\r
+\r
+While we do sets of changes and then that leads to commit series the final\r
+step of running 'git format-patch' somehow leads people writing commit\r
+message to add words 'this patch' to the message...\r
+... or (what just come into my mind) they just think these changes as\r
+patches (is that linux-kernel influence ?)\r
+\r
+To me the commit history does not look like series of patches (but series\r
+of commits or changes -- and changes are usually shown as "diffs") --\r
+patching gives a connotation of fixing something (with glue or gum ;)\r
+\r
+That is how I see it. That doesn't mean I am right there (and in this mailing\r
+list I've been wrong in statistically significant amount (*) of times).\r
+\r
+Un{less,til} decided otherwise I'll continue with delicate efforts to\r
+keep this style issue in the minds of developers; despite (**) informing\r
+me that will be doomed...\r
+\r
+Tomi\r
+\r
+(*) https://en.wikipedia.org/wiki/Statistical_significance\r
+(**) https://en.wikipedia.org/wiki/Wiio%27s_laws\r