From: Marco Stornelli <marco.stornelli@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Vladimir Davydov <vdavydov@parallels.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/19] pramfs
Date: Mon, 09 Sep 2013 20:13:51 +0200 [thread overview]
Message-ID: <522E0FDF.8000108@gmail.com> (raw)
In-Reply-To: <20130908234031.GS12779@dastard>
Il 09/09/2013 01:40, Dave Chinner ha scritto:
> On Sat, Sep 07, 2013 at 10:14:04AM +0200, Marco Stornelli wrote:
>> Hi all,
>>
>> this is an attempt to include pramfs in mainline. At the moment pramfs
>> has been included in LTSI kernel. Since last review the code is more
>> or less the same but, with a really big thanks to Vladimir Davydov and
>> Parallels, the development of fsck has been started and we have now
>> the possibility to correct fs errors due to corruption. It's a "young"
>> tool but we are working on it. You can clone the code from our repos:
>>
>> git clone git://git.code.sf.net/p/pramfs/code pramfs-code
>> git clone git://git.code.sf.net/p/pramfs/Tools pramfs-Tools
>
> The 1980s are calling, and they want their filesytem back. :)
>
> So, Devil's Advocate time. Convince me as to why pramfs should be
> merged.
>
Never used in my embedded project with more of few mb, and maybe you are
asking for cases not targeted. Pramfs is in LTSI not why I asked Greg to
include it, but because there are several companies asked me to do. The
message wasn't "hey, pramfs is in LTSI, so we must include it in
mainline" but it was only a consideration and indication that there is
need of something like that out there. Sure we can talk about if it's
the best option or not, however this is the real world. In addition,
this comment is exactly why the kernel community is not really friendly
to be time-to-market, we have to say it. It's not possible to have a 10
years review. It's a never ending story. Maybe when there is a big
company behind a patch the behavior is different and I can do several
examples, but I don't want to say more, life is hard, I know, even in
the kernel community. I think I can close the review here, my delusion
is not for me, I can live well in each case, but for the companies and
all the people believes in the project.
Thanks to all.
Marco
next prev parent reply other threads:[~2013-09-09 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 8:14 [PATCH 00/19] pramfs Marco Stornelli
2013-09-07 14:58 ` richard -rw- weinberger
2013-09-07 16:22 ` Marco Stornelli
2013-09-08 9:05 ` Vladimir Davydov
2013-09-08 9:34 ` Marco Stornelli
2013-09-08 6:49 ` Marco Stornelli
2013-09-08 23:40 ` Dave Chinner
2013-09-09 18:13 ` Marco Stornelli [this message]
2013-09-09 23:28 ` Dave Chinner
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=522E0FDF.8000108@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vdavydov@parallels.com \
/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).