X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=hkRPbAkEl/KTTWmT
	7sB2+J+aybeIto3dKtNfhGl6i3et3gwqs+AzFKMITGypCBMruHGg/5LBI6Q60P7q
	OcZV/G+0kQGda+WU0Y2UZwE4+syCFYMroN1Sfka7mOilIPNCYwGXO74PvZ4fkw7x
	nFDUmvwxg9uscF6Hw/R9qOW+SRU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=eXYyBfYvSX/aXO91DHkgcD
	MXIE4=; b=Y9boHhG3hA1uaeyqEEeSrCQ0LJ8jDUmt8vX25WuWS4uQ7/skEltrbn
	EAENSMvECMkOc27fAERqfbLl4JY4BezoxYMyGXng5Xz4Qa/5SDY+WYe7MT0Z04LU
	BswPxBusxA9fhKCI5Tm79F7yxsEONsi5VkK0DZjXrNZQvmYOODWcA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=Walsh, walsh, Canada, voice
X-HELO: smtp-out-no.shaw.ca
Reply-To: Brian.Inglis@SystematicSw.ab.ca
Subject: Re: Posting Order (was: Getting error message...)
To: cygwin@cygwin.com
References: <1308285295.576965.1549657291745.ref@mail.yahoo.com> <1308285295.576965.1549657291745@mail.yahoo.com> <387708835.666318.1549693636691@mail.yahoo.com> <744398867.20190209163623@yandex.ru> <5C5EE7D2.2010404@tlinx.org>
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Openpgp: preference=signencrypt
Message-ID: <8135ed8a-993f-52ee-e914-b15d13a90a12@SystematicSw.ab.ca>
Date: Sat, 9 Feb 2019 11:26:09 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <5C5EE7D2.2010404@tlinx.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 2019-02-09 07:46, L A Walsh wrote:
> That's why it is very surprising to see computer people treat
> 'email' as a "log" instead of like a chat w/history...

Logs can be displayed most recent first, as with directories or lists in most
products, and chats with history are in chronological order, so...

> Anyway...I'm not so sure I see the benefit of starting to read
> sometime in the past -- especially in the case of a 90
> page support interaction.  Would you really want to read
> 90 pages before you started participating in a discussion?
> 
> Technical lists are not fiction books that are read for fun,
> they are usually where people look to see if something 
> applies by reading the first paragraph or two -- which wouldn't
> be the most recent stuff, by far.
I expect top posting for corporate stuff, with explicit CC lists, mainly on one
corporate server, where nobody reads past the first sentence anyway, or trimming
the old cruft, so you had better repeat everything you need there, similar to
leaving voice mail messages.

I expect bottom posting and trimming for subscriber or volunteer groups like
this, to respect the time and effort of those doing the work, and reduce the
bandwidth distributed across the internet (or Usenet if gatewayed via NNTP - I
still have *LOW* limits on downloaded message size from fighting early spam
blasts there).

Neither group of recipients is going to bother with previous message content,
(unless they are a recent CC added to a long thread, and sometimes not then).

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

