linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Lukas Czerner <lczerner@redhat.com>, linux-ext4@vger.kernel.org
Cc: tytso@mit.edu
Subject: Re: [PATCH] e2fsprogs: Remove any occurrence of ext4dev and test_fs
Date: Tue, 17 Feb 2015 16:34:57 -0600	[thread overview]
Message-ID: <54E3C211.1080207@redhat.com> (raw)
In-Reply-To: <54175D1E.9090107@redhat.com>

On 9/15/14 4:41 PM, Eric Sandeen wrote:
> On 2/19/14 10:56 AM, Eric Sandeen wrote:
>> On 2/19/14, 8:57 AM, Lukas Czerner wrote:
>>> ext4dev is no longer supported by kernel so we really need to get rid of
>>> it entirely from e2fsprogs.
>>>
>>> This patch removes any occurrence of ext4dev and test_fs flag from the
>>> e2fsprogs tools with one exception. Out of paranoia we can still leave
>>> the possibility to remove test_fs flag (EXT2_FLAGS_TEST_FILESYS) from
>>> the file system using e2fsck by specifying clear_test_fs_flag option in
>>> the e2fsck.config file.
>>
>> Yes, I think this makes good sense.  While one could argue that
>> test_fs may be used for some other purpose in the future, we have
>> added a lot of fairly experimental code without making use of it,
>> so I'd argue that it has no practical use going forward.
>>
>> Acked-by: Eric Sandeen <sandeen@redhat.com>
> 
> Ted, any thoughts on this?

I was going to wait for the 1-year anniversary of patch submission, but
decided to jump the gun by 2 days.  ;)

Ted, do you plan to merge this patch, or should I take it off our radar.

Thanks,
-Eric


      reply	other threads:[~2015-02-17 22:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 14:57 [PATCH] e2fsprogs: Remove any occurrence of ext4dev and test_fs Lukas Czerner
2014-02-19 16:56 ` Eric Sandeen
2014-03-03 12:55   ` Lukáš Czerner
2014-09-15 21:41   ` Eric Sandeen
2015-02-17 22:34     ` Eric Sandeen [this message]

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=54E3C211.1080207@redhat.com \
    --to=sandeen@redhat.com \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --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 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).