From: Greg 'groggy' Lehey <grog@lemis.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Mail etiquette (was: SunOS code?)
Date: Thu, 6 Sep 2018 13:21:09 +1000 [thread overview]
Message-ID: <20180906032109.GC76566@eureka.lemis.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1809060933040.28912@aneurin.horsfall.org>
[-- Attachment #1: Type: text/plain, Size: 2026 bytes --]
On Thursday, 6 September 2018 at 9:40:30 +1000, Dave Horsfall wrote:
> On Wed, 5 Sep 2018, Gilles Gravier wrote:
>
>> (Henri, you're in copy of this again, because first time I did a Reply
>> instead of Reply to list/all. Sorry.)
>
> One of my pet hates is people who use "Reply All" because either they are
> too lazy to edit the Reply (and they top-post, too), or the list is set up
> that way.
That's a matter of opinion. Many people consider it good manners to
specifically mention people participating in a discussion. For
example,
https://www.freebsd.org/doc/en_US.ISO8859-1/articles/freebsd-questions/article.html#idp53204040
specifically states:
Unless there is a good reason to do otherwise, reply to the sender
and to FreeBSD-questions [the list].
> I really don't need my own personal copy, as well as a list copy.
That's what procmail is for.
> Oh, and people who are too lazy to trim their replies too, because
> they are encouraged to top-post.
Yes, that's in that URL too:
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.
Also another thing that I still think very important:
If the submitter did not abide by format conventions (lines too
long, inappropriate subject line), please fix it. In the case of an
incorrect subject line (such as âHELP!!??â), change the subject line
to (say) âRe: Difficulties with sync PPP (was: HELP!!??)â. That way
other people trying to follow the thread will have less difficulty
following it.
That doesn't explicitly address the issue of change of topic within a
thread, but it should.
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2018-09-06 3:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 21:34 [TUHS] SunOS code? Noel Chiappa
2018-08-31 1:59 ` Kevin Bowling
2018-08-31 21:34 ` Cág
2018-08-31 21:39 ` Clem Cole
2018-08-31 21:47 ` Arthur Krewat
2018-08-31 21:57 ` Warner Losh
2018-08-31 21:58 ` Larry McVoy
2018-08-31 22:02 ` Warner Losh
2018-08-31 22:19 ` Cág
2018-08-31 22:23 ` Jon Forrest
2018-08-31 22:30 ` Cág
2018-08-31 22:34 ` Jon Forrest
2018-09-01 10:46 ` Donald ODona
2018-08-31 22:20 ` Cág
2018-08-31 23:02 ` Arthur Krewat
2018-09-01 1:57 ` Larry McVoy
2018-09-01 3:23 ` Theodore Y. Ts'o
2018-09-01 16:29 ` Kevin Bowling
2018-09-01 16:35 ` Larry McVoy
2018-09-01 19:32 ` Clem Cole
2018-09-01 16:27 ` Kevin Bowling
2018-09-01 17:17 ` Arthur Krewat
2018-09-01 22:19 ` Theodore Y. Ts'o
2018-09-02 5:05 ` Kevin Bowling
2018-09-02 19:43 ` Theodore Y. Ts'o
2018-09-04 11:47 ` Kevin Bowling
2018-09-04 17:39 ` Gilles Gravier
2018-09-04 17:45 ` Henry Bent
2018-09-05 6:31 ` Gilles Gravier
2018-09-05 12:55 ` Arthur Krewat
2018-09-05 15:26 ` Warner Losh
2018-09-05 15:36 ` Chet Ramey
2018-09-05 15:43 ` Arthur Krewat
2018-09-05 23:40 ` Dave Horsfall
2018-09-06 3:21 ` Greg 'groggy' Lehey [this message]
2018-09-05 0:10 ` Tony Finch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180906032109.GC76566@eureka.lemis.com \
--to=grog@lemis.com \
--cc=dave@horsfall.org \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).