From: Richard Weinberger <richard.weinberger@gmail.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
Richard Weinberger <richard.weinberger@gmail.com>,
Gao Xiang <hsiangkao@aol.com>,
Richard Weinberger <richard@nod.at>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-erofs@lists.ozlabs.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: erofs: Question on unused fields in on-disk structs
Date: Thu, 22 Aug 2019 16:29:44 +0200 [thread overview]
Message-ID: <CAFLxGvzGEBH2Z+Bpv68OMeLR1JH0pe6bHn6P-sBG+epLTXbR6w@mail.gmail.com> (raw)
In-Reply-To: <20190822142142.GB2730@mit.edu>
On Thu, Aug 22, 2019 at 4:21 PM Theodore Y. Ts'o <tytso@mit.edu> wrote:
> It might make life easier for other kernel developers if "features"
> was named "compat_features" and "requirements" were named
> "incompat_features", just because of the long-standing use of that in
> ext2, ext3, ext4, ocfs2, etc. But that naming scheme really is a
> legacy of ext2 and its descendents, and there's no real reason why it
> has to be that way on other file systems.
Yes, the naming confused me a little. :-)
--
Thanks,
//richard
next prev parent reply other threads:[~2019-08-22 14:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 17:10 erofs: Question on unused fields in on-disk structs Richard Weinberger
2019-08-19 17:10 ` Richard Weinberger
2019-08-19 17:10 ` Richard Weinberger
2019-08-19 20:45 ` Gao Xiang
2019-08-19 20:45 ` Gao Xiang via Linux-erofs
2019-08-21 21:37 ` Richard Weinberger
2019-08-21 21:37 ` Richard Weinberger
2019-08-21 22:03 ` Gao Xiang
2019-08-21 22:03 ` Gao Xiang via Linux-erofs
2019-08-22 8:33 ` Richard Weinberger
2019-08-22 8:33 ` Richard Weinberger
2019-08-22 9:05 ` Gao Xiang
2019-08-22 9:05 ` Gao Xiang
2019-08-22 9:08 ` Gao Xiang
2019-08-22 9:08 ` Gao Xiang
2019-08-22 14:21 ` Theodore Y. Ts'o
2019-08-22 14:21 ` Theodore Y. Ts'o
2019-08-22 14:29 ` Richard Weinberger [this message]
2019-08-22 14:29 ` Richard Weinberger
2019-08-22 14:38 ` Gao Xiang
2019-08-22 14:38 ` Gao Xiang
2019-08-22 14:34 ` Gao Xiang
2019-08-22 14:34 ` Gao Xiang
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=CAFLxGvzGEBH2Z+Bpv68OMeLR1JH0pe6bHn6P-sBG+epLTXbR6w@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=hsiangkao@aol.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.