From: "Pali Rohár" <pali.rohar@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Andreas Bombe <andreas.bombe@gmail.com>,
Andreas Henriksson <andreas@fatal.se>,
Jaroslav Skarvada <jskarvad@redhat.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
util-linux@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mpluskal@suse.com, base-system@gentoo.org,
Karel Zak <kzak@redhat.com>, Andreas Bombe <aeb@debian.org>,
Andreas Dilger <adilger@dilger.ca>
Subject: Re: Future of dosfstools project (FAT)
Date: Mon, 14 Jan 2019 16:17:09 +0100 [thread overview]
Message-ID: <20190114151709.xemy2h4gtgtsos3d@pali> (raw)
Message-ID: <20190114151709.wtHMlXJaxG_a8feXU9UL8T2vjuE__jnXoEJoKZKzHZk@z> (raw)
In-Reply-To: <2431182.t5fd7Oadsi@blindfold>
On Tuesday 08 January 2019 16:39:04 Richard Weinberger wrote:
> Am Dienstag, 8. Januar 2019, 16:32:55 CET schrieb Andy Shevchenko:
> > On Fri, Dec 28, 2018 at 12:18 AM Pali Rohár <pali.rohar@gmail.com> wrote:
> > > On Monday 17 December 2018 10:50:04 Pali Rohár wrote:
> > > > On Wednesday 12 December 2018 14:57:36 Pali Rohár wrote:
> >
> > > > Thanks for review of #94! As next you can take #92 from list.
> > >
> > > Andreas, can you look at next pull requests?
> >
> > Looking from a side how slow this is being processed I think the best
> > option to fork and abandon the old project if author / maintainer by
> > some reason wouldn't like to give a push rights.
>
> +1
I really do not want to create fork or become new "maintainer" of this
project.
If somebody else want to take project or create fork, I can prepare
patches and send them to new place. But still I would like to see code
review of patches from other people. dosfstools is a project which is
used by lot of people and is de-facto standard for FAT32 Linux support.
So breaking something should be prevented as much as possible.
Richard or Andy, if Andreas really do not have time for dosfstools, what
about you to take maintenance of dosfstools?
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2019-01-14 15:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 8:40 Future of dosfstools project (FAT) Pali Rohár
2018-10-01 20:00 ` Andreas Dilger
2018-10-01 20:13 ` Richard Weinberger
2018-10-02 8:16 ` Pali Rohár
2018-10-02 8:44 ` Jaroslav Skarvada
2018-10-12 9:19 ` Andreas Henriksson
2018-10-12 12:40 ` Pali Rohár
2018-10-12 14:35 ` Doug Goldstein
2018-11-14 11:33 ` Pali Rohár
[not found] ` <CAPXf_qN66-Mi+o+9ENGqCDe-_2tHaf9uM3moRcCGNvmxwH3ExQ@mail.gmail.com>
2018-12-06 8:38 ` Pali Rohár
2018-12-12 13:57 ` Pali Rohár
2018-12-17 9:50 ` Pali Rohár
2018-12-27 22:17 ` Pali Rohár
2019-01-08 15:32 ` Andy Shevchenko
2019-01-08 15:39 ` Richard Weinberger
2019-01-14 15:17 ` Pali Rohár [this message]
2019-01-14 15:17 ` Pali Rohár
2019-01-14 15:19 ` Richard Weinberger
2019-01-14 15:19 ` Richard Weinberger
2019-02-09 15:40 ` Pali Rohár
2019-02-15 20:04 ` Andy Shevchenko
2018-10-02 9:36 ` Karel Zak
2018-10-01 20:14 ` Pali Rohár
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=20190114151709.xemy2h4gtgtsos3d@pali \
--to=pali.rohar@gmail.com \
--cc=adilger@dilger.ca \
--cc=aeb@debian.org \
--cc=andreas.bombe@gmail.com \
--cc=andreas@fatal.se \
--cc=andy.shevchenko@gmail.com \
--cc=base-system@gentoo.org \
--cc=jskarvad@redhat.com \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpluskal@suse.com \
--cc=richard@nod.at \
--cc=util-linux@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).