Re: [PATCH 0/9] Fix directory lookup on read-only databases

diff --git a/0c/1fc56a49e3c8d1a7ea93090882b4a96b23b7f9 b/0c/1fc56a49e3c8d1a7ea93090882b4a96b23b7f9
new file mode 100644 (file)
index 0000000..604a708
--- /dev/null
+++ b/0c/1fc56a49e3c8d1a7ea93090882b4a96b23b7f9
@@ -0,0 +1,80 @@
+Return-Path: <teythoon@jade-hamburg.de>\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 4D2AC431FD0\r
+       for <notmuch@notmuchmail.org>; Wed, 23 May 2012 03:29:56 -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 Jd8zvFEJBB4T for <notmuch@notmuchmail.org>;\r
+       Wed, 23 May 2012 03:29:55 -0700 (PDT)\r
+Received: from mail.cryptobitch.de (cryptobitch.de [88.198.7.68])\r
+       (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id B34FC431FAF\r
+       for <notmuch@notmuchmail.org>; Wed, 23 May 2012 03:29:55 -0700 (PDT)\r
+Received: from mail.jade-hamburg.de (mail.jade-hamburg.de [85.183.11.228])\r
+       (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by mail.cryptobitch.de (Postfix) with ESMTPSA id 24F1551150C\r
+       for <notmuch@notmuchmail.org>; Wed, 23 May 2012 12:29:54 +0200 (CEST)\r
+Received: by mail.jade-hamburg.de (Postfix, from userid 401)\r
+       id 88BF3DF2A3; Wed, 23 May 2012 12:29:53 +0200 (CEST)\r
+Received: from thinkbox.jade-hamburg.de (thinkbox.jadE-Hamburg.de\r
+ [10.1.1.153]) (using TLSv1 with cipher AES256-SHA (256/256 bits))     (No client\r
+ certificate requested) (Authenticated sender: teythoon)       by\r
+ mail.jade-hamburg.de (Postfix) with ESMTPSA id A1E3ADF2A0;    Wed, 23 May 2012\r
+ 12:29:52 +0200 (CEST)\r
+Received: from teythoon by thinkbox.jade-hamburg.de with local (Exim 4.77)\r
+       (envelope-from <teythoon@thinkbox.jade-hamburg.de>)\r
+       id 1SX8oC-0007TA-Up; Wed, 23 May 2012 12:28:48 +0200\r
+Content-Type: text/plain; charset="utf-8"\r
+MIME-Version: 1.0\r
+Content-Transfer-Encoding: quoted-printable\r
+From: Justus Winter <4winter@informatik.uni-hamburg.de>\r
+User-Agent: alot/0.3+\r
+To: Austin Clements <amdragon@MIT.EDU>,  notmuch@notmuchmail.org\r
+References: <1337314423-3702-1-git-send-email-amdragon@mit.edu>\r
+In-Reply-To: <1337314423-3702-1-git-send-email-amdragon@mit.edu>\r
+Message-ID: <20120523102848.10967.53020@thinkbox.jade-hamburg.de>\r
+Subject: Re: [PATCH 0/9] Fix directory lookup on read-only databases\r
+Date: Wed, 23 May 2012 12:28:48 +0200\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: Wed, 23 May 2012 10:29:56 -0000\r
+\r
+Hi Austin :)\r
+\r
+Quoting Austin Clements (2012-05-18 06:13:33)\r
+> This fixes notmuch_database_get_directory and\r
+> notmuch_database_find_message_by_filename so that they don't attempt\r
+> to create missing directory documents.  This makes them work on\r
+> read-only databases (and prevents n_d_f_m_b_f from crashing\r
+> unceremoniously on read-only databases).\r
+\r
+Thanks for taking care of this, this patch series looks good.\r
+\r
+> If we do a 0.13.1 bug fix release, these patches could go in to\r
+> complement the API changes made in 0.13 to support these fixes.  David\r
+> can make that call.\r
+\r
+I'd support this.\r
+\r
+Cheers,\r
+Justus\r