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 216F4431FBC for ; Fri, 10 Oct 2014 02:12:09 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] 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 pxCJkeXlevAU for ; Fri, 10 Oct 2014 02:12:01 -0700 (PDT) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 58B51431FAF for ; Fri, 10 Oct 2014 02:12:01 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1XcWEu-0006FE-HF; Fri, 10 Oct 2014 06:11:56 -0300 Received: (nullmailer pid 19440 invoked by uid 1000); Fri, 10 Oct 2014 09:11:50 -0000 From: David Bremner To: Rama , notmuch@notmuchmail.org Subject: Re: thread id specification In-Reply-To: <1412898994.37246.177261393.5FA4747A@webmail.messagingengine.com> References: <1412898994.37246.177261393.5FA4747A@webmail.messagingengine.com> User-Agent: Notmuch/0.18.1+98~gae27403 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Fri, 10 Oct 2014 11:11:50 +0200 Message-ID: <87k348l25l.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain 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, 10 Oct 2014 09:12:09 -0000 Rama writes: > Can anyone in-the-know shed some light on how notmuch generates its > thread ids? Until recently, I'd only seen numeric thread ids 16 > characters long, padded with zeroes. For example: > > thread:0000000000000001 > thread:0000000000000002 > thread:0000000000000005 > etc etc > > Today, several new threads were created with non numeric ids: > > thread:000000000000000d > thread:000000000000000e > thread:000000000000000f > Those are numbers too, just hexadecimal. d