From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Linux Manual Pages <linux-man@vger.kernel.org>
Subject: Re: Add sub-topic on 'exFAT' in man mount
Date: Tue, 21 Nov 2023 07:55:25 -0600 [thread overview]
Message-ID: <20231121135525.cdildqelcqrnt3ze@illithid> (raw)
In-Reply-To: <ZVyBmFI_TvmJkaN1@devuan>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
At 2023-11-21T11:08:17+0100, Alejandro Colomar wrote:
> On Tue, Nov 21, 2023 at 01:48:14PM +0700, Bagas Sanjaya wrote:
> > Please don't top-post, reply inline with appropriate context instead.
>
> And the mandatory example. :)
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
In corporate communications it can make sense to top-post (and not
remove any quoted material, no matter how irrelevant). I won't
elaborate here, because this is not a venue for corporate
communications. But I have seen some programmers over-apply the above
preference and humor in contexts where there are reasons not to do so.
Only you can stop Dunning-Krugerism in its tracks! ;-)
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-21 13:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 22:55 Add sub-topic on 'exFAT' in man mount Seamus de Mora
2023-11-20 23:33 ` Alejandro Colomar
2023-11-20 23:44 ` Seamus de Mora
2023-11-21 6:48 ` Bagas Sanjaya
2023-11-21 10:08 ` Alejandro Colomar
2023-11-21 11:41 ` Bagas Sanjaya
2023-11-21 12:51 ` Alejandro Colomar
2023-11-21 13:57 ` Bagas Sanjaya
2023-11-21 13:55 ` G. Branden Robinson [this message]
2023-11-21 16:41 ` Seamus de Mora
2023-11-21 6:55 ` Bagas Sanjaya
2023-11-26 23:59 ` Namjae Jeon
2023-11-27 22:43 ` Seamus de Mora
2023-12-05 7:49 ` Seamus de Mora
2023-12-05 9:03 ` Bagas Sanjaya
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=20231121135525.cdildqelcqrnt3ze@illithid \
--to=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.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