mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Filesystems Development <linux-fsdevel@vger.kernel.org>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
	Christian Brauner <brauner@kernel.org>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH 0/5] Documentation: sharedsubtree: reST massaging
Date: Fri, 29 Aug 2025 16:41:49 -0600	[thread overview]
Message-ID: <87ecst3g42.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250819061254.31220-1-bagasdotme@gmail.com>

Bagas Sanjaya <bagasdotme@gmail.com> writes:

> Hi,
>
> Shared subtree docs is converted with minimal markup changes to reST in commit
> cf06612c65e5dc ("docs: filesystems: convert sharedsubtree.txt to ReST"). The
> formatting, however, is still a rather rough and can be improved.
>
> Let's polish it.

I have applied the set, thanks.

jon

      parent reply	other threads:[~2025-08-29 22:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-19  6:12 Bagas Sanjaya
2025-08-19  6:12 ` [PATCH 1/5] Documentation: sharedsubtree: Format remaining of shell snippets as literal code blcoks Bagas Sanjaya
2025-08-19  6:12 ` [PATCH 2/5] Documentation: sharedsubtree: Use proper enumerator sequence for enumerated lists Bagas Sanjaya
2025-08-19  6:12 ` [PATCH 3/5] Documentation: sharedsubtree: Don't repeat lists with explanation Bagas Sanjaya
2025-08-19  6:12 ` [PATCH 4/5] Documentation: sharedsubtree: Align text Bagas Sanjaya
2025-08-19  6:12 ` [PATCH 5/5] Documentation: sharedsubtree: Convert notes to note directive Bagas Sanjaya
2025-08-29 22:41 ` Jonathan Corbet [this message]

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=87ecst3g42.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=bagasdotme@gmail.com \
    --cc=brauner@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=rdunlap@infradead.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

all inboxes | Powered by JetHome®