Re: Reply all - issue

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