From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/6] xfs_io.8: rearrange command listings by section
Date: Wed, 28 Nov 2018 15:34:59 -0800 [thread overview]
Message-ID: <20181128233459.GD8131@magnolia> (raw)
In-Reply-To: <8c568cb2-4931-288c-0be3-68bd5caef634@sandeen.net>
On Wed, Nov 28, 2018 at 04:39:47PM -0600, Eric Sandeen wrote:
> On 11/9/18 6:45 PM, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > Most of the commands listed under "OTHER COMMANDS" apply to files or
> > filesystems. Create two new sections for that and populate them
> > appropriately.
> >
> > Here's what moves:
> >
> > fsmap: moves from file io commands to filesystem commands
> > utimes: moves from file io commands to file commands
> >
> >>From the OTHER COMMANDS section:
> >
> > lsattr/chattr: moves to file commands
> > flink: moves to file commands
> > stat/statx: moves to file commands
> > lsproj/chproj: moves to file commands
> > parent: moves to file commands
> > [gs]et_encpolicy: moves to file io commands
> > freeze/thaw: move to filesystem commands
> > inject: move to filesystem commands
> > resblks: move to filesystem commands
> > shutdown: move to filesystem commands
> > statfs: move to filesystem commands
> > label: move to filesystem commands
>
> Thank you for getting this better organized. Of course, I have
> some questions. :)
>
> What does "FILE COMMANDS" vs. "FILE I/O COMMANDS" mean, exactly?
> I ask because for example bmap & fiemap are still under FILE IO but
> they... really don't do file IO. What's your intended distinction
> with these new sections?
Admittedly, it's been a looong time since I wrote this patch.
Um... I think my intent was for FILE COMMANDS to pertain to file
attributes, whereas FILE I/O COMMANDS would pertain to reading, writing,
encoding, mapping, and otherwise messing with the contents of a file.
--D
>
> Thanks,
> -Eric
next prev parent reply other threads:[~2018-11-29 10:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 0:45 [PATCH 0/6] xfsprogs-4.20: various fixes Darrick J. Wong
2018-11-10 0:45 ` [PATCH 1/6] xfs_io.8: rearrange command listings by section Darrick J. Wong
2018-11-28 22:39 ` Eric Sandeen
2018-11-28 23:34 ` Darrick J. Wong [this message]
2018-11-28 23:46 ` Eric Sandeen
2018-12-05 3:21 ` [PATCH 1/6 V2] " Eric Sandeen
2018-12-05 17:56 ` Darrick J. Wong
2018-11-10 0:45 ` [PATCH 2/6] xfs_repair: don't error out on dirs with a single leafn block Darrick J. Wong
2018-11-22 18:13 ` [PATCH v2 " Darrick J. Wong
2018-12-05 3:48 ` Eric Sandeen
2018-12-05 4:11 ` Eric Sandeen
2018-12-05 16:48 ` Darrick J. Wong
2018-12-05 16:54 ` Eric Sandeen
2018-11-10 0:45 ` [PATCH 3/6] xfs_repair: skip block reservation when fixing freelist Darrick J. Wong
2018-11-10 7:22 ` Allison Henderson
2018-11-28 23:34 ` Eric Sandeen
2018-11-10 0:45 ` [PATCH 4/6] xfs_scrub: handle totally empty inode chunks Darrick J. Wong
2018-11-10 7:19 ` Allison Henderson
2018-11-29 0:16 ` Eric Sandeen
2018-11-29 0:35 ` Darrick J. Wong
2018-11-29 0:38 ` Eric Sandeen
2018-11-10 0:45 ` [PATCH 5/6] xfs_scrub: fix fractional reporting of single inodes Darrick J. Wong
2018-11-10 7:15 ` Allison Henderson
2018-11-10 17:52 ` Darrick J. Wong
2018-11-10 0:45 ` [PATCH 6/6] xfs_scrub: move everything to /usr/sbin Darrick J. Wong
2018-11-10 6:45 ` Allison Henderson
2018-11-10 8:43 ` L A Walsh
2018-11-10 18:06 ` Darrick J. Wong
2018-11-27 23:15 ` [PATCH 7/6] xfs_db: add missing string name for DBM_COWDATA Darrick J. Wong
2018-11-29 0:37 ` Eric Sandeen
2018-11-29 0:54 ` [PATCH v2 " Darrick J. Wong
2018-11-29 5:24 ` Eric Sandeen
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=20181128233459.GD8131@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).