From: Christoph Hellwig <hch@infradead.org>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Lennart Poettering <lennart@poettering.net>,
dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: btrfs_inode_item's otime?
Date: Sat, 10 Jan 2015 02:17:03 -0800 [thread overview]
Message-ID: <20150110101703.GA5385@infradead.org> (raw)
In-Reply-To: <8849914.dEW4UQEyXo@merkaba>
On Sat, Jan 10, 2015 at 11:13:52AM +0100, Martin Steigerwald wrote:
> What is the issue with the xstat, new stat format stuff? Basically I have the
> feeling that this is in discussion for at least 5 years or so and I always
> wondered where it is stuck. I am not aware of any discussions of it recently,
> but I may have overseen those.
It's mostly because it turned on into an exercise of blatant
overengineering. The primary need in the stat area is a few new fields,
and the secondary interesting one is to allow the user to request only
some field that it actually needs (i.e. statlite). But all the
proposals included bullshit like variable length fields, xattrs and
similar and thus were totally off the table.
prev parent reply other threads:[~2015-01-10 10:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 17:21 btrfs_inode_item's otime? Lennart Poettering
2015-01-06 11:47 ` Chris Samuel
2015-01-06 12:43 ` Chris Samuel
2015-01-06 18:41 ` David Sterba
2015-01-08 10:52 ` Chris Samuel
2015-01-09 16:11 ` David Sterba
2015-01-15 10:48 ` David Sterba
2015-01-16 4:47 ` Chris Samuel
2015-01-06 18:26 ` David Sterba
2015-01-07 13:57 ` Lennart Poettering
2015-01-07 14:42 ` Christoph Hellwig
2015-01-10 10:13 ` Martin Steigerwald
2015-01-10 10:17 ` Christoph Hellwig [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=20150110101703.GA5385@infradead.org \
--to=hch@infradead.org \
--cc=Martin@lichtvoll.de \
--cc=dsterba@suse.cz \
--cc=lennart@poettering.net \
--cc=linux-btrfs@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).