From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS2044 198.145.29.0/24 X-Spam-Status: No, score=-3.4 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id EBEF120248 for ; Wed, 13 Mar 2019 23:07:08 +0000 (UTC) Received: from localhost (unknown [12.208.228.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5063121019; Wed, 13 Mar 2019 23:07:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1552518428; bh=+YIJTYVFHAEDsFg/xWnFw/1u35V+K/5QWWt+FHa/6zs=; h=Date:From:To:Cc:Subject:From; b=ZeYJWOKDLvZkBezpFYjFytBFd9wx0S92jo8sBKOQ97nRxONDcDUnDcQO7YaaOsfNA /yVX11KJWwaUcIVRli/Z9bGlawsnKo2Mx7BBIdlxbiFSN0I9PlLgVVbKY0Ep2bm2Km yoWi6g2g+L/NpWEWKGk7qoUgXT65gHBxf66ZrcM8= Date: Wed, 13 Mar 2019 18:07:07 -0500 From: Bjorn Helgaas To: Eric Wong Cc: meta@public-inbox.org Subject: Threading in git repo? Message-ID: <20190313230707.GB210027@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: Hi Eric, As far as I can tell, pi git repos have no branching: each new message is added as a child commit of the most recent message, even if it is a response to an older message. Have you considered making the new message a child of the message it is responding to? I'm fiddling with making neomutt read a pi git repo. Currently I only read the git log info (not the commit bodies). It's pretty fast to read the author, date, and subject (since you conveniently stash them in the commit metadata), but since I'm not reading the mail headers, neomutt can't do all its threading magic. It seems like working out the threading could be done once at the time the message is added to the git repo, and threads could appear as branches in the repo. Bjorn