From: Norbert Veber <nveber@pyre.virge.net>
To: David Sterba <dsterba@suse.cz>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs: extended inode refs
Date: Thu, 31 Jan 2013 13:25:26 -0500 [thread overview]
Message-ID: <20130131182526.GC14605@pyre.virge.net> (raw)
In-Reply-To: <20130131173404.GN30535@twin.jikos.cz>
On Thu, Jan 31, 2013 at 06:34:04PM +0100, David Sterba wrote:
> Otherwise, Mark's patches add the incompat bit unconditionally, we need
> a way how to make it tunable in the same way as other mkfs do. I'd say
> to take them as-is now and extend mkfs later.
Well I guess its more of a job for btrfstune. Same way as tune2fs can
enable all of their features.
Having to reformat seems uncecessary.
next prev parent reply other threads:[~2013-01-31 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 15:33 btrfs: extended inode refs Norbert Veber
2013-01-31 17:34 ` David Sterba
2013-01-31 18:25 ` Norbert Veber [this message]
2013-02-01 12:37 ` David Sterba
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=20130131182526.GC14605@pyre.virge.net \
--to=nveber@pyre.virge.net \
--cc=dsterba@suse.cz \
--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).