From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id B60F0431FAF for ; Wed, 30 Jan 2013 13:39:47 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.799 X-Spam-Level: X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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 IUIXj84xhiK4 for ; Wed, 30 Jan 2013 13:39:47 -0800 (PST) Received: from mail-we0-f179.google.com (mail-we0-f179.google.com [74.125.82.179]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 2B8D6431FAE for ; Wed, 30 Jan 2013 13:39:47 -0800 (PST) Received: by mail-we0-f179.google.com with SMTP id x43so1608701wey.24 for ; Wed, 30 Jan 2013 13:39:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=do2gsLgOwTgn6Tz5AuHPOnX9BhJLTw6N88bdJ6kk0xA=; b=o9rFv7Cdj5Z4oGDHdDVAjS5SAQLnK+qZYxYnjcFq18j0RpyMEVfqk01tc9W4KFtLwM AQXCsF44fKMG1sUGYZepqNPh7KPBJZBrTcRImFHZFl6AjoUTI7/5OzOrlER4hiYWvScq S48ImcXYtwkwaJRVBNSSzysphlzitsMpcvQrpBBoxzQm1B2N9h3/H+5GcYh1SffmTRGS YT5uKR/klgYsbHoCEdu4XYxdj3LIn7W/TJZj7nK8DPK9g3c3wrK1aNXT9aeuZUOUZTf5 jdRxq0apPfnQ24LHqMwVuKuzfC+lDW0PxrTAukNDEkpWReLsXL4GZXn5t1wQYAHlphba KEyg== X-Received: by 10.180.85.103 with SMTP id g7mr11324584wiz.29.1359581984535; Wed, 30 Jan 2013 13:39:44 -0800 (PST) Received: from kuru.dyndns-at-home.com (AAnnecy-651-1-13-37.w90-27.abo.wanadoo.fr. [90.27.180.37]) by mx.google.com with ESMTPS id bd7sm5577165wib.8.2013.01.30.13.39.42 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 30 Jan 2013 13:39:43 -0800 (PST) Sender: suvayu ali Date: Wed, 30 Jan 2013 22:39:40 +0100 From: Suvayu Ali To: notmuch@notmuchmail.org Subject: Re: Reply all - issue Message-ID: <20130130213940.GC434@kuru.dyndns-at-home.com> Mail-Followup-To: notmuch@notmuchmail.org References: <000001cdfcd9$82500f00$86f02d00$@nl> <87wquxjq7k.fsf@nikula.org> <002601cdfd83$83b283f0$8b178bd0$@nl> <87boc8bt8a.fsf@yoom.home.cworth.org> <00bf01cdff0d$4ecedd10$ec6c9730$@nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00bf01cdff0d$4ecedd10$ec6c9730$@nl> User-Agent: Mutt/1.5.21 (2011-07-01) 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: Wed, 30 Jan 2013 21:39:47 -0000 Hi, I am a *very new* notmuch user (notmuch + mutt-kz/Emacs), but I would like to throw in a few opinions about this topic. On Wed, Jan 30, 2013 at 06:14:48PM +0100, Robert Mast wrote: > Thanks for your clear explanation. > > The thread-merging and breaking is in the procedure already pointed at by > Jani: (_notmuch_database_link_message() in lib/database.cc.) > > Is there a quick way to recognize those git-threads by subject-syntax, or to > reliably tag them to exclude them from subject-breaking? > I don't like this feature at all. Threads with patches from git-send-email are not the only kind of threads where this might be relevant. Often I encounter threads with sub-threads which are a little OT hence get renamed, but they are still related to the parent thread. Sometimes this helps in following how a topic came up while discussing something else. This is especially true when going through old emails for reference. I have encountered this in mailing lists, personal emails and discussions with colleagues. One of the many other reasons for me to switch from Gmail to my present setup was to avoid this "feature". That said, I think this feature is indeed useful at times but it should be implemented in the UI on user command or as a configurable (e.g. mutt provides the command), not a default underlying behaviour of the backend. If this is pursued, implementing it as a configurable in the Emacs UI might be more appropriate (or whatever other UIs exists out there). Hope this is constructive to the discussion. :) Cheers, -- Suvayu Open source is the future. It sets us free.