From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [e2fsprogs PATCH 0/6] chattr.1 updates
Date: Mon, 18 Nov 2019 12:20:06 -0500 [thread overview]
Message-ID: <20191118172006.GD27585@mit.edu> (raw)
In-Reply-To: <20191118014852.390686-1-ebiggers@kernel.org>
On Sun, Nov 17, 2019 at 05:48:46PM -0800, Eric Biggers wrote:
> This series updates the chattr(1) man page to document the verity file
> attribute ('V'), improve the documentation for the encryption file
> attribute ('E'), and make a few other cleanups.
>
> Eric Biggers (6):
> chattr.1: document the verity attribute
> chattr.1: adjust documentation for encryption attribute
> chattr.1: add casefold attribute to mode string
> chattr.1: fix some grammatical errors
> chattr.1: clarify that ext4 doesn't support tail-merging either
> chattr.1: say "cleared" instead of "reset"
>
> misc/chattr.1.in | 40 +++++++++++++++++++++++++---------------
> 1 file changed, 25 insertions(+), 15 deletions(-)
Thanks for the updates to the chattr man page. I've applied it to the
maint branch.
- Ted
prev parent reply other threads:[~2019-11-18 17:20 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 ` [PATCH 6/6] chattr.1: say "cleared" instead of "reset" Eric Biggers
2019-11-18 17:20 ` Theodore Y. Ts'o [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=20191118172006.GD27585@mit.edu \
--to=tytso@mit.edu \
--cc=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).