From: Theodore Tso <tytso@MIT.EDU>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH e2fsprogs] teach libblkid about ext4(dev)
Date: Tue, 22 Jan 2008 18:25:22 -0500 [thread overview]
Message-ID: <20080122232522.GF1659@mit.edu> (raw)
In-Reply-To: <4796780F.1000603@redhat.com>
On Tue, Jan 22, 2008 at 05:11:11PM -0600, Eric Sandeen wrote:
> Returns ext4dev for now; will need to change to ext4 at the appropriate
> time I guess.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Hmm... see my test_fs patch. If we decide that this is a good way to
go, then we can use the presence of that flag to cause blkid to return
"ext4dev", and absence of that flag for blkid to return "ext4".
When we rename the kernel filesystem type from ext4dev to ext4, we
also take out the requirement for EXT2_FLAGS_TEST_FILESYS, and simply
tell people to remove that flag from their ext4 filesytems. Blkid
will then do the right thing without requiring us to synchronize
updating the kernel as well as e2fsprogs at the same time.
What do people think? I think it's a pretty elegant solution.
- Ted
next prev parent reply other threads:[~2008-01-22 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 23:11 [PATCH e2fsprogs] teach libblkid about ext4(dev) Eric Sandeen
2008-01-22 23:25 ` Theodore Tso [this message]
2008-01-27 3:27 ` Theodore Tso
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=20080122232522.GF1659@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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