From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Mark Harmstone <maharmstone@meta.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2] btrfs-progs: add --subvol option to mkfs.btrfs
Date: Wed, 31 Jul 2024 09:14:23 +0930 [thread overview]
Message-ID: <469357d5-45af-4e7d-818f-056fe79a14b1@gmx.com> (raw)
In-Reply-To: <60aa212c-c1f1-478e-a108-1201ff5fb5ef@gmx.com>
在 2024/7/31 06:34, Qu Wenruo 写道:
>
>
> 在 2024/7/30 23:20, Mark Harmstone 写道:
>> Thanks Qu.
>>
>> On 30/7/24 10:55, Qu Wenruo wrote:
>>> And before the --subvolume option, I'm more intesrested in getting rid
>>> of the function completely.
>>
>> With respect, I'd appreciate it if you waited for a version of this
>> patch to be upstreamed before doing any refactoring.
>
> But I really do not like the way new subvolumes are created.
>
> If we merge it for now, it will take way more time to change/fix it.
> I do not think that's how we do the development.
Just to be more clear, I'm not against all your awesome work on bringing
the new feature to mkfs.
It's the fact that we're making the --rootdir feature more and more like
a subset of FUSE btrfs implementation.
In that case, there is too much historic burden left to the code base,
and I believe it's the time to clean them up, other than building more
and more things on an unstable base and hoping new comers will clean
them up.
So please really consider making the existing code better, before
pushing a new feature for --rootdir option.
And the inode size calculating part is definitely not a proper thing
that would appear in a FUSE/kernel fs implementation, even it works fine
for now.
Thanks,
Qu
>
> Thanks,
> Qu
>
>>
>> Thanks
>>
>> Mark
>>
>
next prev parent reply other threads:[~2024-07-30 23:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 9:38 [PATCH v2] btrfs-progs: add --subvol option to mkfs.btrfs Mark Harmstone
2024-07-30 9:55 ` Qu Wenruo
2024-07-30 13:50 ` Mark Harmstone
2024-07-30 21:04 ` Qu Wenruo
2024-07-30 23:44 ` Qu Wenruo [this message]
2024-07-31 13:45 ` Josef Bacik
2024-07-31 22:30 ` Qu Wenruo
2024-07-31 15:02 ` Josef Bacik
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=469357d5-45af-4e7d-818f-056fe79a14b1@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=maharmstone@meta.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