linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-ext4@vger.kernel.org
Subject: [PATCH 6/6] chattr.1: say "cleared" instead of "reset"
Date: Sun, 17 Nov 2019 17:48:52 -0800	[thread overview]
Message-ID: <20191118014852.390686-7-ebiggers@kernel.org> (raw)
In-Reply-To: <20191118014852.390686-1-ebiggers@kernel.org>

From: Eric Biggers <ebiggers@google.com>

Setting a bit to 0 is normally called "clearing", not "resetting"; and
chattr.1 already says "clear" in some places.  Use "clear" consistently.

Signed-off-by: Eric Biggers <ebiggers@google.com>
---
 misc/chattr.1.in | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/misc/chattr.1.in b/misc/chattr.1.in
index 870397ae..66e791db 100644
--- a/misc/chattr.1.in
+++ b/misc/chattr.1.in
@@ -115,7 +115,7 @@ the blocks on disk.  It may not be removed using
 .BR chattr (1).
 .PP
 A file, directory, or symlink with the 'E' attribute set is encrypted by the
-filesystem.  This attribute may not be set or reset using
+filesystem.  This attribute may not be set or cleared using
 .BR chattr (1),
 although it can be displayed by
 .BR lsattr (1).
@@ -132,7 +132,7 @@ Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE
 capability can set or clear this attribute.
 .PP
 The 'I' attribute is used by the htree code to indicate that a directory
-is being indexed using hashed trees.  It may not be set or reset using
+is being indexed using hashed trees.  It may not be set or cleared using
 .BR chattr (1),
 although it can be displayed by
 .BR lsattr (1).
@@ -146,7 +146,8 @@ attribute has no effect.  Only the superuser or a process possessing the
 CAP_SYS_RESOURCE capability can set or clear this attribute.
 .PP
 A file with the 'N' attribute set indicates that the file has data
-stored inline, within the inode itself. It may not be set or reset using
+stored inline, within the inode itself. It may not be set or cleared
+using
 .BR chattr (1),
 although it can be displayed by
 .BR lsattr (1).
@@ -193,7 +194,7 @@ A file with the 'V' attribute set has fs-verity enabled.  It cannot be
 written to, and the filesystem will automatically verify all data read
 from it against a cryptographic hash that covers the entire file's
 contents, e.g. via a Merkle tree.  This makes it possible to efficiently
-authenticate the file.  This attribute may not be set or reset using
+authenticate the file.  This attribute may not be set or cleared using
 .BR chattr (1),
 although it can be displayed by
 .BR lsattr (1).
-- 
2.24.0


  parent reply	other threads:[~2019-11-18  1:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-18  1:48 [e2fsprogs PATCH 0/6] chattr.1 updates Eric Biggers
2019-11-18  1:48 ` [PATCH 1/6] chattr.1: document the verity attribute Eric Biggers
2019-11-18  1:48 ` [PATCH 2/6] chattr.1: adjust documentation for encryption attribute Eric Biggers
2019-11-18  1:48 ` [PATCH 3/6] chattr.1: add casefold attribute to mode string Eric Biggers
2019-11-18  1:48 ` [PATCH 4/6] chattr.1: fix some grammatical errors Eric Biggers
2019-11-18  1:48 ` [PATCH 5/6] chattr.1: clarify that ext4 doesn't support tail-merging either Eric Biggers
2019-11-18  1:48 ` Eric Biggers [this message]
2019-11-18 17:20 ` [e2fsprogs PATCH 0/6] chattr.1 updates Theodore Y. Ts'o

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=20191118014852.390686-7-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=linux-ext4@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).