linux-kernel - Re: Future of dosfstools project (FAT)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFLxGvxfegQFh0kvk81VLhLh0AkgvpT=hWMDCJz5FmgoTUNRqA@mail.gmail.com>
Date:   Mon, 1 Oct 2018 22:13:41 +0200
From:   Richard Weinberger <richard.weinberger@...il.com>
To:     adilger@...ger.ca
Cc:     Pali Rohár <pali.rohar@...il.com>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        util-linux@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        andy.shevchenko@...il.com, Karel Zak <kzak@...hat.com>,
        aeb@...ian.org, andreas.bombe@...il.com
Subject: Re: Future of dosfstools project (FAT)

On Mon, Oct 1, 2018 at 10:01 PM Andreas Dilger <adilger@...ger.ca> wrote:
> If the current dosfstools maintainer is non-responsive, you could always
> fork the project in GitHub, land the critical patches into your branch,
>  and make a release on your own.  If the maintainer surfaces again, then
> they can pull in your patches.  If not, then you are the new maintainer.

I also recommend talking to package maintainers of major distros.
Maybe one of them forked the project already and did what you plan to do.

In any case, let's try to avoid a drama like util-linux-ng was.

-- 
Thanks,
//richard