Return-Path: 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 E270F431FD0 for ; Fri, 3 Jun 2011 13:05:07 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0.01 X-Spam-Level: X-Spam-Status: No, score=0.01 tagged_above=-999 required=5 tests=[T_MIME_NO_TEXT=0.01] 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 hKUkiUW3VL9T for ; Fri, 3 Jun 2011 13:05:07 -0700 (PDT) Received: from arlo.cworth.org (arlo.cworth.org [50.43.72.2]) by olra.theworths.org (Postfix) with ESMTP id 1F619431FB6 for ; Fri, 3 Jun 2011 13:05:06 -0700 (PDT) Received: from yoom.home.cworth.org (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 65F8B29A604; Fri, 3 Jun 2011 13:05:01 -0700 (PDT) Received: by yoom.home.cworth.org (Postfix, from userid 1000) id 1F90E25417E; Fri, 3 Jun 2011 13:05:01 -0700 (PDT) From: Carl Worth To: Dmitry Kurochkin , Notmuch Mail Subject: Re: [PATCH 14/25] Fix old style notmuch-fcc-dirs configuration check. In-Reply-To: <87lixkpw16.fsf@gmail.com> References: <1306619520-25730-1-git-send-email-jrollins@finestructure.net> <1306619520-25730-2-git-send-email-jrollins@finestructure.net> <1306619520-25730-3-git-send-email-jrollins@finestructure.net> <1306619520-25730-4-git-send-email-jrollins@finestructure.net> <1306619520-25730-5-git-send-email-jrollins@finestructure.net> <1306619520-25730-6-git-send-email-jrollins@finestructure.net> <1306619520-25730-7-git-send-email-jrollins@finestructure.net> <1306619520-25730-8-git-send-email-jrollins@finestructure.net> <1306619520-25730-9-git-send-email-jrollins@finestructure.net> <1306619520-25730-10-git-send-email-jrollins@finestructure.net> <1306619520-25730-11-git-send-email-jrollins@finestructure.net> <1306619520-25730-12-git-send-email-jrollins@finestructure.net> <1306619520-25730-13-git-send-email-jrollins@finestructure.net> <1306619520-25730-14-git-send-email-jrollins@finestructure.net> <1306619520-25730-15-git-send-email-jrollins@finestructure.net> <874o48yg28.fsf@yoom.home.c worth.org> <87lixkpw16.fsf@gmail.com> User-Agent: Notmuch/0.5 (http://notmuchmail.org) Emacs/23.3.1 (i486-pc-linux-gnu) Date: Fri, 03 Jun 2011 13:05:00 -0700 Message-ID: <87oc2ellzn.fsf@yoom.home.cworth.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 20:05:08 -0000 --=-=-= On Thu, 02 Jun 2011 10:49:57 +0400, Dmitry Kurochkin wrote: > Well, it says that changes are in notmuch 0.5. So "old" and "previous" > refer to pre-0.5 (i.e. 0.4) and "new" refers to 0.5. Sure, but I happen to ahve already forgotten the details of how the variable could be configured in 0.4 and in 0.5. More importantly, anyone in the future reading the commit log is much more likely not to remember. > Any configuration when `notmuch-fcc-dirs' is a list. That variable has > a nice documentation. Again, I'd like our commit messages to be self-contained. They are much more useful if the describe the change being made without assuming to much outside knowledge. > > It would be easier to understand the code if there were a corresponding > > test case for it. ... > I do not think we need a test for this fix. What we need are tests for > FCC functionality when notmuch-fcc-dirs is a list. Yes! > Old configuration format was changed in 0.5 in an incompatible way. > There is a check for the unsupported old-style configuration. But the > check is broken and results in an error when running with a valid > new-style configuration. This is actually what I meant by "corresponding test case". If the bug here is that a "new-style configuration" doesn't work , (and I still don't like that wording---don't say "new style"---explain what it actually *is*), then yes, we need a test case showing that bug. > I am not sure what you expect from the commit message here. IMO it is > enough for this small bugfix and those who interested can always refer > to documentation for details. The commit message should provide a self-contained description of the change. It should be along the lines of: When fcc-dirs is set to notmuch was incorecctly detecting this as the and generating an error message. Fix the test so that this configuration now works. Where the above should be replaced with actual descriptions, not relative pointers to information like "old style" or "new style". Does that make sense? -Carl --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk3pPmwACgkQ6JDdNq8qSWggNwCfUZIISt65QlMf1PZ3c+x22s6/ LlMAn1r3/eY8b1ov4Z4rmnkbjMG8pA7Q =/kso -----END PGP SIGNATURE----- --=-=-=--