From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] befs: remove unused endian functions
Date: Wed, 01 Jun 2016 20:44:55 +0100 [thread overview]
Message-ID: <574F3B37.5000103@osg.samsung.com> (raw)
In-Reply-To: <20160601123849.baf7149a7c391d9195e06f93@linux-foundation.org>
On 01/06/16 20:38, Andrew Morton wrote:
> On Wed, 01 Jun 2016 20:31:04 +0100 Luis de Bethencourt <luisbg@osg.samsung.com> wrote:
>
>> Do you have any suggestions of more modest projects within other file systems?
>> Something that would be a better time investment.
>
> Nope, sorry :(. Reading the linux-fsdevel archives might be
> worthwhile - look for unaddressed bug reports. Also
> bugzilla.kernel.org and the various distro bugzilla archives may dredge
> out issues that remain unaddressed.
>
I will do that, I had subscribed to that mailing list but it isn't very active.
Reading the archives is a good idea.
Thanks Andrew, appreciate your time.
Will finish reading the befs code, because it is fun :)
Maybe I will do some cleanup, to help the unmaintained file system. But you are
right that adding write support is too much.
Luis
prev parent reply other threads:[~2016-06-01 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 13:27 [PATCH] befs: remove unused endian functions Luis de Bethencourt
2016-05-31 20:54 ` Al Viro
2016-05-31 20:59 ` Luis de Bethencourt
2016-06-01 19:20 ` Andrew Morton
2016-06-01 19:31 ` Luis de Bethencourt
2016-06-01 19:38 ` Andrew Morton
2016-06-01 19:44 ` Luis de Bethencourt [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=574F3B37.5000103@osg.samsung.com \
--to=luisbg@osg.samsung.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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