On Tue, Nov 22, 2016 at 04:54:58PM +0800, Anand Jain wrote: > On 11/14/16 20:13, David Sterba wrote: > > On Tue, Nov 08, 2016 at 09:14:39PM +0800, Anand Jain wrote: > >> This patch isn't integrated, any idea why ? > > > > Because it does not cover all usecases. > > You have stated one of the use case here > https://www.spinics.net/lists/linux-btrfs/msg49391.html > > which I have it implemented in these patches > [PATCH 5/7] btrfs-progs: introduce framework version to features > [PATCH 6/7] btrfs-progs: add -O comp= option for mkfs.btrfs > [PATCH 7/7] btrfs-progs: add -O comp= option for btrfs-convert > > was their more ? Yeah, it turned out there's more. > > I've committed the preparatory > > bits from branch where I've been working on that feature so we can > > actually get to the hard parts. > > these patch set is a year old as well. are you planning to drop > these patches ? the clarity is missing. IMO. Preparatory bits are in patches: btrfs-progs: mkfs: add names of matching sysfs feature names btrfs-progs: mkfs: enhance feature table btrfs-progs: mkfs: extend mkfs features with compat, safe and default versions the core work is not yet done. The original usecase has been extended to allow for selecting features that are compatible, ie. can be mounted, safe, ie. are ok wrt The Status page, and default, ie. automatically selected by mkfs. Additionally to that, a system-wide preset from a config file in /etc. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
