linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-doc@vger.kernel.org, Jan Kara <jack@suse.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: filesystems: Reduce ext2.rst to one top-level heading
Date: Mon, 9 Nov 2020 11:27:55 +0100	[thread overview]
Message-ID: <20201109102755.GB21934@quack2.suse.cz> (raw)
In-Reply-To: <20201108004045.1378676-1-j.neuschaefer@gmx.net>

On Sun 08-11-20 01:40:45, Jonathan Neuschäfer wrote:
> This prevents the other headings like "Options" and "Specification" from
> leaking out and being listed separately in the table of contents.
> 
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>

Thanks! I'll queue this fix into my tree.

								Honza

> ---
>  Documentation/filesystems/ext2.rst | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/filesystems/ext2.rst b/Documentation/filesystems/ext2.rst
> index d83dbbb162e20..c2fce22cfd035 100644
> --- a/Documentation/filesystems/ext2.rst
> +++ b/Documentation/filesystems/ext2.rst
> @@ -1,6 +1,7 @@
>  .. SPDX-License-Identifier: GPL-2.0
> 
> 
> +==============================
>  The Second Extended Filesystem
>  ==============================
> 
> --
> 2.28.0
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      reply	other threads:[~2020-11-09 10:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-08  0:40 [PATCH] docs: filesystems: Reduce ext2.rst to one top-level heading Jonathan Neuschäfer
2020-11-09 10:27 ` Jan Kara [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=20201109102755.GB21934@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=corbet@lwn.net \
    --cc=j.neuschaefer@gmx.net \
    --cc=jack@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).