From: John Cowan <cowan@ccil.org>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: The AWK Programming Language, 2nd Ed.: What's new?
Date: Fri, 15 Sep 2023 16:09:20 -0400 [thread overview]
Message-ID: <CAD2gp_R3JNcB9=iRe4fuW301+t4jn56AM+VHpV6tW_cT8J7NCw@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2309160602540.55293@aneurin.horsfall.org>
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
On Fri, Sep 15, 2023 at 4:04 PM Dave Horsfall <dave@horsfall.org> wrote:
> Are you really commenting upon the contents of someone's signature block?
>
My view has always been that it's okay to comment on them (within reason)
but not okay to complain about them. In a .sig block, people can talk
about whatever they want, as long as the block itself is not BUAFed or
otherwise warlord-worthy.
[-- Attachment #2: Type: text/html, Size: 943 bytes --]
next prev parent reply other threads:[~2023-09-15 20:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 21:28 arnold
2023-09-15 1:40 ` Mary Ann Horton
2023-09-15 3:48 ` arnold
2023-09-16 17:52 ` Mary Ann Horton
2023-09-15 3:49 ` Ajay Shah
2023-09-15 3:54 ` arnold
2023-09-15 9:09 ` KenUnix
2023-09-15 11:24 ` Dan Cross
2023-09-15 20:04 ` Dave Horsfall
2023-09-15 20:09 ` John Cowan [this message]
2023-09-15 20:17 ` Warren Toomey via TUHS
2023-09-16 17:32 ` Mary Ann Horton
2023-09-15 21:08 ` Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2023-09-16 1:20 Norman Wilson
2023-09-09 19:51 [TUHS] " markus schnalke
2023-09-09 20:13 ` [TUHS] " christopher fujino
2023-09-10 19:41 ` arnold
2023-09-10 19:59 ` Norman Wilson
2023-09-11 5:59 ` markus schnalke
2023-09-11 13:52 ` Stuff Received
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='CAD2gp_R3JNcB9=iRe4fuW301+t4jn56AM+VHpV6tW_cT8J7NCw@mail.gmail.com' \
--to=cowan@ccil.org \
--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).