From: "Pali Rohár" <pali.rohar@gmail.com>
To: Andreas Bombe <andreas.bombe@gmail.com>
Cc: Andreas Henriksson <andreas@fatal.se>,
Jaroslav Skarvada <jskarvad@redhat.com>,
linux-fsdevel@vger.kernel.org, util-linux@vger.kernel.org,
linux-kernel@vger.kernel.org, mpluskal@suse.com,
base-system@gentoo.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Karel Zak <kzak@redhat.com>, Andreas Bombe <aeb@debian.org>,
Andreas Dilger <adilger@dilger.ca>,
Richard Weinberger <richard.weinberger@gmail.com>
Subject: Re: Future of dosfstools project (FAT)
Date: Mon, 17 Dec 2018 10:50:04 +0100 [thread overview]
Message-ID: <20181217095004.c6c6itvyfp7cf3ta@pali> (raw)
In-Reply-To: <20181212135736.xtb57r2eatqsgenb@pali>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
On Wednesday 12 December 2018 14:57:36 Pali Rohár wrote:
> On Thursday 06 December 2018 09:38:28 Pali Rohár wrote:
> > On Thursday 06 December 2018 01:53:02 Andreas Bombe wrote:
> > > Pali Rohár <pali.rohar@gmail.com> schrieb am Mi., 14. Nov. 2018 um
> > > 12:33 Uhr:
> > >
> > > > And... has somebody else time to look at those pending patches and do
> > > > some initial review? I would really appreciate if somebody look and
> > > > comment them.
> > > >
> > > > There are 14 open pull requests:
> > > > https://github.com/dosfstools/dosfstools/pulls
> > >
> > >
> > > I'll spend time on this again. It would help if you could make a list of
> > > higher priority PRs you would like see being looked at first.
> >
> > So.. here is some list:
> >
> > https://github.com/dosfstools/dosfstools/pull/92
> > https://github.com/dosfstools/dosfstools/pull/93
> > https://github.com/dosfstools/dosfstools/pull/94
> > https://github.com/dosfstools/dosfstools/pull/101
> > https://github.com/dosfstools/dosfstools/pull/104
> > https://github.com/dosfstools/dosfstools/pull/84
>
> Maybe you can start with Year 2038 problem in PR 94:
> https://github.com/dosfstools/dosfstools/pull/94
Thanks for review of #94! As next you can take #92 from list.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2018-12-17 9:50 UTC|newest]
Thread overview: 21+ 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 [this message]
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
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=20181217095004.c6c6itvyfp7cf3ta@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.weinberger@gmail.com \
--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).