public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Seamus de Mora <seamusdemora@gmail.com>,
	Linux Manual Pages <linux-man@vger.kernel.org>
Subject: Re: Add sub-topic on 'exFAT' in man mount
Date: Tue, 21 Nov 2023 18:41:41 +0700	[thread overview]
Message-ID: <ZVyXdZ0MYBFyr1xG@archie.me> (raw)
In-Reply-To: <ZVyBmFI_TvmJkaN1@devuan>

[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]

On Tue, Nov 21, 2023 at 11:08:17AM +0100, Alejandro Colomar wrote:
> Hi Seamus, Bagas,
> 
> [I'm reordering to better reply.]
> 
> 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?

Thanks for the pro tip! I was adapting my above message from broonie [1].

> 
> > On Mon, Nov 20, 2023 at 05:44:40PM -0600, Seamus de Mora wrote:
> > > Uh, OK... stupid question first: Where is ./CONTRIBUTING?
> > 
> > It is in man-pages.git tree [1].
> > 
> > Thanks.
> > 
> > [1]: https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING
> 
> Yes, it is in the root of the source code repository.  Since you sent
> the mail to the correct addresses (alx@ and linux-man@), I assumed you
> had read at least the head(1) of that file, since it's the only place I
> know that documents that.  I'm now curious: how did you know the
> addresses to write to?

Observing the mailing list [2] AND read that file in man-page.git tree.
For the kernel proper, I always look in MAINTAINERS.

Thanks.

[1]: https://lore.kernel.org/all/ZI2jhXUMv9QYmL94@finisterre.sirena.org.uk/
[2]: https://lore.kernel.org/linux-man

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-11-21 11:41 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 [this message]
2023-11-21 12:51           ` Alejandro Colomar
2023-11-21 13:57             ` Bagas Sanjaya
2023-11-21 13:55         ` G. Branden Robinson
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=ZVyXdZ0MYBFyr1xG@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=seamusdemora@gmail.com \
    /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