linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 2/2 V2] e2fsprogs: revise and extend chattr(1) and chattr usage()
Date: Fri, 4 Jul 2014 23:05:27 -0400	[thread overview]
Message-ID: <20140705030527.GF11103@thunk.org> (raw)
In-Reply-To: <53A44679.4020001@redhat.com>

On Fri, Jun 20, 2014 at 09:34:33AM -0500, Eric Sandeen wrote:
> The chattr(1) manpage and chattr usage() output were missing some flags.
> 
> Add those, and make some other minor cosmetic fixes.
> 
> (I've left out the 'B' (EXT2_COMPRBLK_FL) flag, because
> it's not actually used anywhere, and I can't figure out
> how it differs from 'c' (EXT2_COMPR_FL))
> 
> Also, because the matrix of filesystems & flags is quite large,
> refer to filesystem-specific manpages for detailed discussion
> of flags supported by those filesystems, rather than trying to
> cover it all in this manpage.  I'll send those manpage
> updates to the appropriate lists a bit later.
> 
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>

Applied, thanks.

					- Ted

      parent reply	other threads:[~2014-07-05  3:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 23:15 [PATCH 1/2] e2fsprogs: reorder flags in chattr(1) Eric Sandeen
2014-06-19 23:17 ` [PATCH 1/2 V2] " Eric Sandeen
2014-06-20 18:45   ` Andreas Dilger
2014-07-05  3:05   ` Theodore Ts'o
2014-06-19 23:24 ` [PATCH 2/2] e2fsprogs: revise and extend chattr(1) and chattr usage() Eric Sandeen
2014-06-20  5:27   ` Andreas Dilger
2014-06-20 14:34   ` [PATCH 2/2 V2] " Eric Sandeen
2014-06-20 18:44     ` Andreas Dilger
2014-07-05  3:05     ` Theodore 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=20140705030527.GF11103@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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).