Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Dennis Lee Bieber <wlfraed@ix.netcom.com>
Newsgroups: comp.lang.python
Subject: Re: Question on compiling on linux
Date: Mon, 27 Jun 2016 20:01:10 -0400
Organization: IISS Elusive Unicorn
Lines: 54
Message-ID: <mailman.47.1467072087.2358.python-list@python.org>
References: <CAPTjJmqe-PK=ZhT=cVRDgdvGnsfkAyOV0G=TUY62ij_YJUKiJw@mail.gmail.com> <576D79B8.5080303@chello.at> <CAPTjJmrN4+5RuPB8PAAzG8f5aA0VRV=9xk8ybVtT5_6pz=Nnhg@mail.gmail.com> <576D7D67.3070804@chello.at> <576D89D7.6010409@chello.at> <CAKJDb-NVSy3Gi85cu3LU-oaJFCvvGmxnsaUCLNsxxTde=F1o_Q@mail.gmail.com> <576E389B.7060709@chello.at> <CAKJDb-MwyATu-PG=BZgUZOvreiwzPM3OQFcE3Nh2CJqn4AHd=g@mail.gmail.com> <1467035818.2222949.649673417.18E0D090@webmail.messagingengine.com> <bse3nbt6mhfs9bta25kgphu1inrg8m3hgo@4ax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: list
Xref: csiph.com comp.lang.python:110619

On Mon, 27 Jun 2016 09:56:58 -0400, Random832 <random832@fastmail.com>
declaimed the following:

>On Mon, Jun 27, 2016, at 00:26, Zachary Ware wrote:
>> A: Because you have to read things in reverse order.
>> Q: Why?
>> A: Top-posting.
>> Q: What's one of the most annoying common email practices?
>
>Which is witty, but doesn't *actually* explain why it's bad.
>
>1. The intent, as I understand it, with top-posting is that the reply
>message stands on its own, and the quoted message is just "attached" in
>case someone needs to refer back to it, rather than representing a
>conversational flow as the Q/A format does.
>
	Which is a practice I only saw become popular with M$ Outlook -- which
in many versions makes it nearly impossible to do trim&intersperse
responses.

>2. Most email clients sort messages or threads by date with the most
>recent (or most recently updated) at the top, so there's no generalized
>principle at work against having later things appear above earlier
>things.

	Most email clients also allow one to specify the sort order -- even
Outlook can be told to put oldest at top... 

	The Outlook style works well in a business environment where the
recipient is likely the original sender of the quoted text, and doesn't
need the context -- the quoted copy is just a courtesy copy in this case.

	But for distributed forums -- like Usenet -- with multiple routes from
news server to news server, it is possible for a response from one
server/user [call it svrB] to arrive at a different server [svrC] BEFORE
the original message [from svrA] propagates to [svrC].

	The trim and intersperse/bottom-post is the recommended style in the
"netiquette" RFC https://tools.ietf.org/html/rfc1855 section 3.1.1

"""
    - If you are sending a reply to a message or a posting be sure you
      summarize the original at the top of the message, or include just
      enough text of the original to give a context.  This will make
      sure readers understand when they start to read your response.
      Since NetNews, especially, is proliferated by distributing the
      postings from one host to another, it is possible to see a
      response to a message before seeing the original.  Giving context
      helps everyone.  But do not include the entire original!
"""
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/