--- /dev/null
+Return-Path: <david@tethera.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 56218431FB6\r
+ for <notmuch@notmuchmail.org>; Sat, 23 Aug 2014 15:21:25 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+ autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id Tp059WRUnxwx for <notmuch@notmuchmail.org>;\r
+ Sat, 23 Aug 2014 15:21:18 -0700 (PDT)\r
+Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155])\r
+ (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 3EA37431FAF\r
+ for <notmuch@notmuchmail.org>; Sat, 23 Aug 2014 15:21:18 -0700 (PDT)\r
+Received: from remotemail by yantan.tethera.net with local (Exim 4.80)\r
+ (envelope-from <david@tethera.net>)\r
+ id 1XLJgP-0002Jr-3V; Sat, 23 Aug 2014 19:21:13 -0300\r
+Received: (nullmailer pid 18176 invoked by uid 1000); Sat, 23 Aug 2014\r
+ 22:21:07 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Austin Clements <amdragon@MIT.EDU>, notmuch@notmuchmail.org\r
+Subject: Re: [PATCH v3 04/13] lib: Database version 3: Introduce fine-grained\r
+ "features"\r
+In-Reply-To: <1406859003-11561-5-git-send-email-amdragon@mit.edu>\r
+References: <1406859003-11561-1-git-send-email-amdragon@mit.edu>\r
+ <1406859003-11561-5-git-send-email-amdragon@mit.edu>\r
+User-Agent: Notmuch/0.18.1+72~g028c560 (http://notmuchmail.org) Emacs/24.3.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Sat, 23 Aug 2014 15:21:07 -0700\r
+Message-ID: <87ppfqsv8s.fsf@maritornes.cs.unb.ca>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://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: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 23 Aug 2014 22:21:25 -0000\r
+\r
+Austin Clements <amdragon@MIT.EDU> writes:\r
+> \r
+> + /* Bit mask of features used by this database. Features are\r
+> + * named, independent aspects of the database schema. This is a\r
+> + * bitwise-OR of NOTMUCH_FEATURE_* values (below). */\r
+> + unsigned int features;\r
+\r
+Should we be using a fixed size integer (uint_32t or whatever) for\r
+features? iirc the metadata in the database is actually a string, so I\r
+guess arbitrary precision there.\r
+\r
+> +/* Bit masks for _notmuch_database::features. */\r
+> +enum {\r
+> + /* If set, file names are stored in "file-direntry" terms. If\r
+> + * unset, file names are stored in document data.\r
+> + *\r
+> + * Introduced: version 1. Implementation support: both for read;\r
+> + * required for write. */\r
+> + NOTMUCH_FEATURE_FILE_TERMS = 1 << 0,\r
+\r
+I agree with Jani that the Implementation support: part is a bit\r
+mystifying without the commit message. Maybe part of the commit message\r
+could migrate here? Or maybe just add a pointer to the comment in database.cc.\r
+\r
+> + if (! *incompat_out)\r
+\r
+Should we support passing NULL for incompat_out? or at least check for\r
+it?\r
+\r
+> @@ -1048,7 +1164,8 @@ notmuch_database_get_version (notmuch_database_t *notmuch)\r
+> notmuch_bool_t\r
+> notmuch_database_needs_upgrade (notmuch_database_t *notmuch)\r
+> {\r
+> - return notmuch->needs_upgrade;\r
+> + return notmuch->mode == NOTMUCH_DATABASE_MODE_READ_WRITE &&\r
+> + (NOTMUCH_FEATURES_CURRENT & ~notmuch->features);\r
+> }\r
+\r
+Maybe I'm not thinking hard enough here, but how does this deal with a\r
+feature that is needed to open a database in read only mode? Maybe it\r
+needs a comment for people not as clever as Austin ;).\r
+\r
+d\r
+\r