From: Randy Dunlap <rdunlap@infradead.org>
To: Steve Kenton <skenton@ou.edu>, linux-kernel@vger.kernel.org
Cc: Robert Howard <bob@bcdusa.com>, Jan Kara <jack@suse.com>
Subject: Re: fs/udf and udftools
Date: Wed, 10 Feb 2016 17:56:16 -0800 [thread overview]
Message-ID: <56BBEA40.90202@infradead.org> (raw)
In-Reply-To: <56BBABAC.8010008@ou.edu>
[add Jan Kara]
On 02/10/16 13:29, Steve Kenton wrote:
> Is anyone maintaining these or am I about to volunteer for another job?
CUrrent MAINTAINERS file says:
UDF FILESYSTEM
M: Jan Kara <jack@suse.com>
S: Maintained
F: Documentation/filesystems/udf.txt
F: fs/udf/
and that Doc. file says:
For the latest version and toolset see:
http://linux-udf.sourceforge.net/
> I'm having to dig into fs/udf and udftools/mkudffs as part of a project I'm working on.
> It looks like both have been lacking in personal TLC for quite a while. The changes to
> fs/udf seem to be tree wide VFS work but not updates to things like write support and
> udftools seems to have been frozen for >10 years. Both ~work but I'd like to fix an
> oops I'm getting in udftools and work on adding fallocate() support to fs/udf and then
> feed it back to the community rather than let the changes bit rot locally.
>
> Where to go from here? I've been reading LKML on marc: for years, mainly to see what Linus,
> Al and a variable group of other people say/do but I've never done more than tinker with
> the kernel locally. I'm using git for the project mentioned above but again am not an
> expert but willing to learn. I'm not currently subscribed so please cc me if you could.
>
> smk
>
--
~Randy
next prev parent reply other threads:[~2016-02-11 1:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 21:29 Steve Kenton
2016-02-11 1:56 ` Randy Dunlap [this message]
2016-02-11 2:19 ` Ken Moffat
2016-02-11 3:45 ` Steve Kenton
2016-02-11 10:03 ` Jan Kara
2016-02-11 15:30 ` Steve Kenton
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=56BBEA40.90202@infradead.org \
--to=rdunlap@infradead.org \
--cc=bob@bcdusa.com \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skenton@ou.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
Powered by JetHome