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 6470B4196F2 for ; Thu, 22 Apr 2010 07:06:32 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 p4M-e1PVTFgl for ; Thu, 22 Apr 2010 07:06:31 -0700 (PDT) Received: from homiemail-a21.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by olra.theworths.org (Postfix) with ESMTP id 6A1F8431FC1 for ; Thu, 22 Apr 2010 07:06:31 -0700 (PDT) Received: from sspaeth.de (mtec-hg-docking-1-dhcp-204.ethz.ch [129.132.133.204]) (Authenticated sender: sebastian@sspaeth.de) by homiemail-a21.g.dreamhost.com (Postfix) with ESMTPA id 99332300074 for ; Thu, 22 Apr 2010 07:06:29 -0700 (PDT) Received: by sspaeth.de (sSMTP sendmail emulation); Thu, 22 Apr 2010 16:06:27 +0200 From: "Sebastian Spaeth" To: Notmuch development list Subject: sort order regression Date: Thu, 22 Apr 2010 16:06:27 +0200 Message-ID: <87bpdbmvj0.fsf@SSpaeth.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Thu, 22 Apr 2010 14:06:32 -0000 jkr and I noticed that patch series are shown in reverse order now, in fact threads seem to display messages at the same depth in reverse chronological order now. Here is my monologue from IRC: Is that supposed to show the whole thread in reverse chronological order?: notmuch show --entire-thread id:"1271927251-19867-3-git-send-email-Sebastian@SSpaeth.de" doh, http://git.notmuchmail.org/git/notmuch/commitdiff/f43990ce134d838cdb2cdd5d0752a602e81cfdd9 sort order for within threads used to be SORT_OLDEST_FIRST with that commit it was changed to be inherited from whatever it was (and by default notmuch does NEWEST_FIRST) so that would cause the change IMHO. someone does not seem to have run a test suite there : query.cc sets to NEWEST-FIRST by default. So now we get messages at each depth NEWEST-FIRST. So the code is working as expected. the problem is imho, that we previously had NEWEST_FIRST for top-level and an explicit OLDEST_FIRST within threads < jkr> spaetz: yep. and that explicit OLDEST_FIRST got removed