Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail From: Random832 Newsgroups: comp.lang.python Subject: Re: Meaning and purpose of the Subject field Date: Mon, 21 Dec 2015 23:22:10 -0500 Lines: 14 Message-ID: References: <567887f2$0$1606$c3e8da3$5496439d@news.astraweb.com> <20151222033622.GA67382@cskk.homeip.net> Mime-Version: 1.0 Content-Type: text/plain X-Trace: news.uni-berlin.de rsS+Xc/i7eDy/9trNHGjnAATJmzKQnv31lTtXKnPHLhA== Cancel-Lock: sha1:9VSiJCuAA9h+az/UQgNkyKRCWRE= Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.001 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'sufficient': 0.05; 'imply': 0.07; 'semantic': 0.07; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'thread': 0.10; 'argument': 0.15; '"new': 0.16; 'advocating': 0.16; 'received:80.91.229.3': 0.16; 'received:io': 0.16; 'received:plane.gmane.org': 0.16; 'received:psf.io': 0.16; 'simpson': 0.16; 'threading': 0.16; "wouldn't": 0.16; 'all,': 0.20; 'second': 0.24; 'discussion': 0.24; 'header:User-Agent:1': 0.26; 'header:X-Complaints-To:1': 0.26; 'sense': 0.26; 'thread,': 0.29; 'topic': 0.32; 'changed': 0.33; 'received:comcast.net': 0.33; 'changing': 0.34; 'definition': 0.34; 'but': 0.36; 'should': 0.36; 'there': 0.36; 'to:addr:python-list': 0.36; 'subject:: ': 0.37; 'received:org': 0.37; 'subject:the': 0.39; "didn't": 0.39; 'to:addr:python.org': 0.40; 'clients': 0.61; 'cameron': 0.66; 'subject': 0.70; 'besides,': 0.93 X-Injected-Via-Gmane: http://gmane.org/ X-Gmane-NNTP-Posting-Host: c-68-39-146-59.hsd1.in.comcast.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com comp.lang.python:100717 Cameron Simpson writes: > Besides, changing the Subject line is _supposed_ to break the > threading in these contexts: such clients clearly consider the > discussion topic (subject) as sufficient definition of a thread, and > changing the topic should imply a new thread to such simplistic > clients. This makes sense for the change from "old" to "new (was: old)", which nobody was advocating against (after all, there's semantic content - they wouldn't have changed the subject line if they didn't consider it a new discussion topic), but I think there is a reasonable argument that changing it a second time from "new (was: old)" to "new" is frivolous.