Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Jan 2023 17:01:27 +1100
From:      Greg 'groggy' Lehey <grog@FreeBSD.org>
To:        Paul Procacci <pprocacci@gmail.com>
Cc:        Ian Smith <smithi@nimnet.asn.au>, freebsd-questions@freebsd.org
Subject:   Out of order posting (was:: Load 0.20 on a freshly installed idle system)
Message-ID:  <20230122060127.GB8068@eureka.lemis.com>
In-Reply-To: <CAFbbPui=uPmKoKYo2t2KaXu=yWUT%2Ba4wksqnwvCjJpBsaALcpQ@mail.gmail.com>
References:  <CAGAKwcjmzz%2B6NMaK2YpjWZPB282RvrKV6zQ%2BSLHsDj3zqXwvGw@mail.gmail.com> <CAFbbPuhX%2BrJFLn8ALVNbCujf1tG3DufVWGSknPkJ%2BKdovFq1xQ@mail.gmail.com> <CAGAKwcgFWukBrB_6SZVAoC4YKyPVhVMGED4aB6Z4E1fwZAO6mg@mail.gmail.com> <CAFbbPuhyJDewvE_a6MQpiGrpUew7EtxZKwt_=RHODNUyCYNduw@mail.gmail.com> <CAGAKwcghHH5t1_dtWPkOCwxPvDra%2BmgNFTQsG65i1_7pzTDkug@mail.gmail.com> <CAFbbPujMDQgo=zvSc5orcT=v3ftrVPXDjZE-D%2BUxt3%2BdOjFmUA@mail.gmail.com> <CAGAKwcid8j3C28wiypO87X9HT9Wq8cfTNHWnOQvcQgAcWrFuLw@mail.gmail.com> <CAGAKwcgZz8gujtd8gPBoC5nKxE00q1Pau6%2BiOUjxBR-UMMNpKw@mail.gmail.com> <1889CB4C-4B11-4178-8446-97DA9E5EC35A@nimnet.asn.au> <CAFbbPui=uPmKoKYo2t2KaXu=yWUT%2Ba4wksqnwvCjJpBsaALcpQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--s/l3CgOIzMHHjg/5
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

[message rearranged and trimmed for compliance and legibility]

On Saturday, 21 January 2023 at  1:38:12 -0500, Paul Procacci wrote:
> On Fri, Jan 20, 2023 at 11:44 PM Ian Smith <smithi@nimnet.asn.au> wrote:
>>
>> PS Also bugging me is dreadful endless top-posting, tail-quoting Microso=
ft
>> corporate-email-style mess.
>
> Sorry but blame google and/or gmail for the top posting.

Why?  Have you not read their instructions?  At
https://support.google.com/a/users/answer/9283192 under "Have better
email conversations", there's the item "Reply inline to email".  That
seems to be exactly what we're asking for.

> I use whatever their defaults are and that's not going to change
> unless they change it.

You can put your answer wherever you want, though they may not make it
easy.  But it's your choice to use Gmail.  I'd suggest to put your
answers:

* Where it matches what you're answering.
* Where it matches the project guidelines.

Where are the project guidelines?  Currently there's
https://docs.freebsd.org/en/articles/freebsd-questions/, which contains:

  Include relevant text from the original message. Trim it to the
  minimum, but do not overdo it. It should still be possible for
  somebody who did not read the original message to understand what
  you are talking about.

  Use some technique to identify which text came from the original
  message, and which text you add. I personally find that prepending
  =E2=80=9C>=E2=80=9D to the original message works best. Leaving white spa=
ce after
  the =E2=80=9C> ;=E2=80=9D and leave empty lines between your text and the=
 original
  text both make the result more readable.

  Put your response in the correct place (after the text to which it
  replies). It is very difficult to read a thread of responses where
  each reply comes before the text to which it replies.

> RFC's surrounding usenet described this in pretty clear detail.  (Just
> looked it up: 1855).

Thanks for the link, though I don't see anything that relates to the
current discussion.  About the only thing of relevance I see is:

  do not include the entire original!

> At this point in my life all I would suggest to you is to either
> suck it up or ban/ignore the messages from senders you don't want to
> see.  Mine included.

This would be a rather drastic approach.  Discussion is better.

> I found this to be a better approach than attempting to correct
> people on what is the proper `netiquette'.

Whatever you want, of course.  But if you're prepared to accept a
supposed mandate by Gmail, I wonder how objective you're being.

Greg
--
Sent from my desktop computer.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php

--s/l3CgOIzMHHjg/5
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAmPM0TcACgkQIubykFB6QiONvwCgpllr/MNi/x+4ychETdpW3/CE
vy4An2EgOAvv9PZm8FDbeaItBdDtufhO
=4P1B
-----END PGP SIGNATURE-----

--s/l3CgOIzMHHjg/5--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230122060127.GB8068>