linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <tobin@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Tobin C. Harding" <tobin@kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Mauro Carvalho Chehab <mchehab@s-opensource.com>,
	Neil Brown <neilb@suse.com>, Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v4 7/9] docs: filesystems: vfs: Fix pre-amble indentation
Date: Wed, 15 May 2019 10:29:11 +1000	[thread overview]
Message-ID: <20190515002913.12586-8-tobin@kernel.org> (raw)
In-Reply-To: <20190515002913.12586-1-tobin@kernel.org>

Currently file pre-amble contains custom indentation.  RST is not going
to like this, lets left-align the text.  Put the copyright notices in a
list in preparation for converting document to RST.

Tested-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Tobin C. Harding <tobin@kernel.org>
---
 Documentation/filesystems/vfs.txt | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/filesystems/vfs.txt b/Documentation/filesystems/vfs.txt
index 5c8358c73e30..43b18bafbc20 100644
--- a/Documentation/filesystems/vfs.txt
+++ b/Documentation/filesystems/vfs.txt
@@ -4,12 +4,12 @@
 Overview of the Linux Virtual File System
 =========================================
 
-	Original author: Richard Gooch <rgooch@atnf.csiro.au>
+Original author: Richard Gooch <rgooch@atnf.csiro.au>
 
-		  Last updated on June 24, 2007.
+Last updated on June 24, 2007.
 
-  Copyright (C) 1999 Richard Gooch
-  Copyright (C) 2005 Pekka Enberg
+- Copyright (C) 1999 Richard Gooch
+- Copyright (C) 2005 Pekka Enberg
 
 
 Introduction
-- 
2.21.0


  parent reply	other threads:[~2019-05-15  0:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15  0:29 [PATCH v4 0/9] docs: Convert VFS doc to RST Tobin C. Harding
2019-05-15  0:29 ` [PATCH v4 1/9] docs: filesystems: vfs: Remove space before tab Tobin C. Harding
2019-05-15  0:29 ` [PATCH v4 2/9] docs: filesystems: vfs: Use uniform space after period Tobin C. Harding
2019-05-15  0:29 ` [PATCH v4 3/9] docs: filesystems: vfs: Use 72 character column width Tobin C. Harding
2019-05-15  0:29 ` [PATCH v4 4/9] docs: filesystems: vfs: Use uniform spacing around headings Tobin C. Harding
2019-05-15  0:29 ` [PATCH v4 5/9] docs: filesystems: vfs: Use correct initial heading Tobin C. Harding
2019-05-15  0:29 ` [PATCH v4 6/9] docs: filesystems: vfs: Use SPDX identifier Tobin C. Harding
2019-05-15  0:29 ` Tobin C. Harding [this message]
2019-05-15  0:29 ` [PATCH v4 8/9] docs: filesystems: vfs: Convert spaces to tabs Tobin C. Harding
2019-05-15  0:29 ` [PATCH v4 9/9] docs: filesystems: vfs: Convert vfs.txt to RST Tobin C. Harding
2019-05-29 22:30 ` [PATCH v4 0/9] docs: Convert VFS doc " Jonathan Corbet
2019-05-30  6:01   ` Tobin C. Harding
2019-06-03 23:48   ` Tobin C. Harding
2019-06-04  0:06   ` Tobin C. Harding

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=20190515002913.12586-8-tobin@kernel.org \
    --to=tobin@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@s-opensource.com \
    --cc=neilb@suse.com \
    --cc=rdunlap@infradead.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).