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 0EC88429E21 for ; Sun, 6 Nov 2011 14:01:16 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.699 X-Spam-Level: X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-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 nGozv1-Kt4sW for ; Sun, 6 Nov 2011 14:01:15 -0800 (PST) Received: from mail-iy0-f181.google.com (mail-iy0-f181.google.com [209.85.210.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 99492431FB6 for ; Sun, 6 Nov 2011 14:01:15 -0800 (PST) Received: by iahk25 with SMTP id k25so7164894iah.26 for ; Sun, 06 Nov 2011 14:01:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Y9XLR1G4D0H+Pj2QtyMplibfATxSz+a8IBllAhODOCg=; b=mY6zZivG2MdbpjbCFRQtmpwAjP7Vd8cMO9LjMpY1J4KLpOMa7+rSA4vsW1n+Lv4hwd AVmudIQ3qr9v5M0H6+VUAlaBA0QKb5bT9AONFT5LumTH4UKp/EZ+xERyEO809Qcb1vvk Xya+6l+erA668Y5U2PzuBkjIvnp6C1lst6Rm4= MIME-Version: 1.0 Received: by 10.42.164.194 with SMTP id h2mr39414758icy.44.1320616875106; Sun, 06 Nov 2011 14:01:15 -0800 (PST) Sender: amdragon@gmail.com Received: by 10.143.166.17 with HTTP; Sun, 6 Nov 2011 14:01:14 -0800 (PST) In-Reply-To: <87k47dt0wo.fsf@nikula.org> References: <1320599856-24078-1-git-send-email-amdragon@mit.edu> <87k47dt0wo.fsf@nikula.org> Date: Sun, 6 Nov 2011 17:01:14 -0500 X-Google-Sender-Auth: DM_1f7JZrFE4OZZ6dfxEkwxkQnc Message-ID: Subject: Re: [PATCH] Store "from" and "subject" headers in the database. From: Austin Clements To: Jani Nikula Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: notmuch@notmuchmail.org, notmuch@kismala.com 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: Sun, 06 Nov 2011 22:01:16 -0000 On Sun, Nov 6, 2011 at 4:07 PM, Jani Nikula wrote: > On Sun, =A06 Nov 2011 12:17:36 -0500, Austin Clements = wrote: >> Taking full advantage of this requires a database rebuild, but it will >> fall back to the old behavior for messages that do not have headers >> stored in the database. > > ...what's the most convenient way of rebuilding the database while > preserving my tags etc.? If this was merged, would an older version of > notmuch choke on the rebuilt database with these headers? (To me it > looks like it would be fine.) The standard way to rebuild the database is to do a notmuch dump, move .notmuch out of the way, notmuch new, then notmuch restore. Some day this process should be made automatic. Old versions of notmuch will be blissfully unaware of the new headers stored in the database. They can even safely add messages to an upgraded database without breaking new versions of notmuch.