From nobody Sun Jan 22 17:43:34 2023 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P0LFN3H38z3NGK7 for ; Sun, 22 Jan 2023 17:43:52 +0000 (UTC) (envelope-from 4250.82.1d4f9000227cb8a.588451164a4a2be4f9fe95f31e0e0fdd@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P0LFN2gbyz3Chl for ; Sun, 22 Jan 2023 17:43:52 +0000 (UTC) (envelope-from 4250.82.1d4f9000227cb8a.588451164a4a2be4f9fe95f31e0e0fdd@email-od.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1674409432; x=1677001432; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to:message-id:subject:cc:to:from:date:x-thread-info:subject:to:from:cc:reply-to; bh=VcbmjF1FXdvuIjIAXVfwwVhAtKH+uDAqOiAkZugVAdw=; b=TEQ2gh9WnGNV9sfvcdEszqOFt7gRp68qkxUyo719ypkwgj01a+Dxp8a/vUSjM54NsCG3euVK3IO9vnhfkea3Avk65FqFykg3Iw3vfQCTupLU9chn4wmj3q/km9vea+C7AozbbothtpPWUgbz2IyBXPKSQVWHJuxiE89A2kkOYjo= X-Thread-Info: NDI1MC4xMi4xZDRmOTAwMDIyN2NiOGEucXVlc3Rpb25zPWZyZWVic2Qub3Jn Received: from r3.h.in.socketlabs.com (r3.h.in.socketlabs.com [142.0.180.13]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Sun, 22 Jan 2023 12:43:36 -0500 Received: from smtp.lan.sohara.org (EMTPY [185.202.17.215]) by r3.h.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Sun, 22 Jan 2023 12:43:36 -0500 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.95 (FreeBSD)) (envelope-from ) id 1pJeNS-000HEd-LD; Sun, 22 Jan 2023 17:43:34 +0000 Date: Sun, 22 Jan 2023 17:43:34 +0000 From: Steve O'Hara-Smith To: questions@freebsd.org Cc: doug@safeport.com Subject: Re: Out of order posting (was:: Load 0.20 on a freshly installed idle system) Message-Id: <20230122174334.1e8b75ddc197472a4be3e33d@sohara.org> In-Reply-To: References: <1889CB4C-4B11-4178-8446-97DA9E5EC35A@nimnet.asn.au> <20230122060127.GB8068@eureka.lemis.com> <20230122164001.2cbb15735780a9934989e951@sohara.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4P0LFN2gbyz3Chl X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7381, ipnet:142.0.176.0/22, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Sun, 22 Jan 2023 17:03:10 +0000 (UTC) doug wrote: > Etiquette then, if you like that word better. There is, IMO, no best way. Correct, there is only the appropriate way for each context which is generally to follow the common convention in that context. There are usually good reasons appropriate to the context for those conventions and it is common politeness IMHO to make an effort to fit in with the common conventions in any context. In a similar vein I'd never normally choose to wear a suit, but when expected to be in one to abide by conventions then that's what I'm wearing unless I'm intending to be rude. > Lawyers never delete anything, I guess (as I am not one) it gives a > history of the entire conversation. Some of these emails I am asked to > comment on might be several thousand words long. Do you think bottom > posting is best in this case? Perhaps, and perhaps not - how would I know it's not a context in which I have experience. > If so it really does not matter, as that is not what they think. From this I guess they tend to top post. If it is a typical corporate email chain scenario where people tend to be added to the chain after several exchanges then full quoting is essential and whether the new material is at the top or bottom is a matter of convention with the top being more convenient when keeping up and the bottom more convenient when catching up and since the former is more frequent than the latter top posting tends to dominate these contexts. -- Steve O'Hara-Smith Odds and Ends at http://www.sohara.org/