From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 4825E6DE0C4A for ; Wed, 23 Jan 2019 13:22:35 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.395 X-Spam-Level: X-Spam-Status: No, score=-0.395 tagged_above=-999 required=5 tests=[AWL=-0.195, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uK1XyaWO6ORA for ; Wed, 23 Jan 2019 13:22:34 -0800 (PST) Received: from mail-pf1-f177.google.com (mail-pf1-f177.google.com [209.85.210.177]) by arlo.cworth.org (Postfix) with ESMTPS id 950986DE0C3D for ; Wed, 23 Jan 2019 13:22:34 -0800 (PST) Received: by mail-pf1-f177.google.com with SMTP id 64so1805291pfr.9 for ; Wed, 23 Jan 2019 13:22:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:in-reply-to:references:date:message-id:mime-version; bh=GuqkEUZhm9Knvj9tHVuNYuJWI7bPp/RfiQ/sjlu+Whw=; b=KnAsjIyGkW6aPEpJgBRQjUHv8tIoPK+Eu2H7eJCkqfKM6/t5Xoy48SnfQV1xx/wcXU CIPJZT3uJkI5lzR0i13pV512B7bePuXSHv2lA7UcwHJ6I4EcHuLf84k2KF03NwR2HlxQ KLuU4gm1fUZe+0wuyG7PWJHMgRjWZJsDR18+xdm68pAlQ934iwptR2JIK6cl2G5LkX/m a3DK3KZdM6cZAp3mjFKXXJljjQwZDK4NptwL566wo7uISIu7yHhwX8PZrkNSo00uo2SY 3nxTfXIarPRXqccb1HFcm3xTgYlvO+xU20ywUU7ZaqMZS49JJjJOiovCLtDuuj3ZH1DX 42NA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version; bh=GuqkEUZhm9Knvj9tHVuNYuJWI7bPp/RfiQ/sjlu+Whw=; b=dbg3BDQB1gSpCkkWQCHvfq8bdTsHFwDxOSZ7O/IST6eWmM+K3orArHfohLIvv/sS7l V1zgBGyauJDd+9W72zKfqL6gKXBNvC9ph1lXXfTbbXnlE85K3l0Grz14oYk1FKc8NuAG CItjVe2lF84fA0gRLxrVv38mpFtJFHImJfsJbhYCdFzbJVmu/u24mkU9UIpFjDFvPd5O EOZHILJF7xkPinSC6a9jZUWh24FpUpdBLk8tLkmWELhNv4wJAcqPPYsypyft1DcNweaU i0c+0iBpujgLE2YM4E8Qfo22B2uV0QG+LSSOCkSem6cp3+A2X+LuXqATywq96lgPRYHW 3lfg== X-Gm-Message-State: AJcUukcJ8W8fDRg5kBATN9mLdJTBKjMvr61ocOIBfzdv6eYW7wvfMtBx zZmwG1lR2f2Xa1pBm5ARckc= X-Google-Smtp-Source: ALg8bN4iTFTdqaykHRE+jxtqOVvkUWuBZxnTRk4NflpJH62Fiinb03LIi5Rz6Sj1NLS7ll2AsrkZUg== X-Received: by 2002:a62:2c81:: with SMTP id s123mr3652131pfs.174.1548278553868; Wed, 23 Jan 2019 13:22:33 -0800 (PST) Received: from localhost (c-76-113-28-30.hsd1.nm.comcast.net. [76.113.28.30]) by smtp.gmail.com with ESMTPSA id g28sm31420864pfd.100.2019.01.23.13.22.33 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 23 Jan 2019 13:22:33 -0800 (PST) From: Nicolas Bock To: Daniel Kahn Gillmor , notmuch@notmuchmail.org Subject: Re: merge broken mail threads In-Reply-To: <87h8dz5np2.fsf@fifthhorseman.net> References: <878szbbdfi.fsf@gmail.com> <87h8dz5np2.fsf@fifthhorseman.net> Date: Wed, 23 Jan 2019 14:19:02 -0700 Message-ID: <87va2fgji1.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 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: Wed, 23 Jan 2019 21:22:35 -0000 On Wed, Jan 23 2019, Daniel Kahn Gillmor wrote: > On Wed 2019-01-23 08:29:05 -0700, Nicolas Bock wrote: > >> Sometimes during a lengthy discussion someone inadvertently >> breaks the email thread because their mail client doesn't get >> it. Is there a way to merge the two fragmented threads again >> with notmuch? > > there's a manual way to do it as a janky workaround: > > * create a bogus e-mail message that References: a message-id > from each > split faction. > > * inject that message into your notmuch message store > > * delete that message Nice trick :) Would this also work if I modified the reference of the first email that breaks the thread to point to the email it is quoting? I would have to get notmuch to re-read that email though to update the database. But this approach would not involve first creating a fake message and then deleting it again :) > See also the thread on this maiing list with Subject "thread merge/split > proposal" from back in 2016, starting at > id:87mvp9uwi4.fsf@alice.fifthhorseman.net though i don't think any of > that has been implemented. > > --dkg