From: Christian Stroetmann OntoLab <stroetmann@ontolab.com>
To: Arend Freije <afreije@inn.nl>,
reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Re: reiser4 inclusion?
Date: Mon, 20 Apr 2009 08:35:14 +0200 [thread overview]
Message-ID: <49EC17A2.2060203@ontolab.com> (raw)
In-Reply-To: <49EC1478.2080004@inn.nl>
Dear Arend;
You wrote
> Christian Stroetmann OntoLab wrote:
>
>> Dear Christian;
>> You wrote:
>>
>>> Guys,
>>>
>>> I did NOT intend to start (yet another) /flamewar/ about the pros and
>>> cons of this filesystem. I was really only wondering about the
>>> showstoppers left (i.e. code to fix) before this could be included. I
>>> still imagine that having a (halfway current) TODO list of things
>>> would help a lot here. The KernelJanitors/Todo list looks like a sane
>>> example of what I meant to have.
>>> Bashing around about "renaming the filesystem" and "unfriendly
>>> developers" is not what I consider helpful on this particular matter.
>>>
>>> Thanks,
>>> Christian.
>>>
>>>
>> It seems to be, that we're running in circles since 2 or 3 years.
>>
>
> A complaint about running around in circles is not a showstopper that
> blocks inclusion. Renaming "Reiser4" to "OntoFs" doesn't help either. A
> good Todo list would really be helpful to keep track of the status, to
> trigger feature implementation and/or bug fixes, and to have discussions
> about content, not procedures.
>
> Regards,
>
> Arend
I would like to encourage everybody interested in this subject to first
read the reiserfs-devel mailing-list and my website concerning the R4
filesystem entirely and carefully. If it is helpful and still not clear
what is going on, I'm also willing to write a list of the steps that
have happened.
Sincerely
Christian *<:o)
next prev parent reply other threads:[~2009-04-20 6:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 11:41 reiser4 inclusion? Mat
2009-04-19 20:44 ` Christian Kujau
2009-04-20 4:10 ` Christian Stroetmann OntoLab
[not found] ` <49EC1478.2080004@inn.nl>
2009-04-20 6:35 ` Christian Stroetmann OntoLab [this message]
2009-04-20 6:46 ` Bron Gondwana
-- strict thread matches above, loose matches on Subject: below --
2009-04-18 20:14 Christian Kujau
2009-04-19 10:23 ` Christian Stroetmann OntoLab
2009-04-19 12:51 ` Edward Shishkin
2009-04-19 11:14 ` Bron Gondwana
2009-04-19 11:31 ` Alexander Lyamin
2009-04-19 11:43 ` Mat
2009-04-19 11:47 ` Bron Gondwana
2009-04-19 12:09 ` Dushan Tcholich
2009-04-19 12:32 ` Bron Gondwana
2009-04-19 12:45 ` Alexander Lyamin
2009-04-19 13:00 ` Bron Gondwana
2009-04-19 13:32 ` Alexander Lyamin
2009-04-19 14:00 ` Bron Gondwana
2009-04-19 13:08 ` Dushan Tcholich
2009-04-19 13:24 ` Bron Gondwana
2009-04-24 23:35 ` Jason Todd Slack-Moehrle
2009-04-24 23:53 ` Volker Armin Hemmann
2009-04-25 0:01 ` Jason Todd Slack-Moehrle
2009-04-25 0:15 ` Christian Stroetmann OntoLab
2009-04-25 0:28 ` Volker Armin Hemmann
2009-04-25 0:42 ` Christian Stroetmann OntoLab
[not found] ` <49F2CF9A.1060202@inn.nl>
2009-04-25 9:13 ` Christian Stroetmann OntoLab
2009-04-25 11:16 ` Alli Quaknaa
2009-04-25 16:26 ` Christian Stroetmann OntoLab
[not found] ` <8c113a260904251204u41f90028n975006634ed99e59@mail.gmail.com>
2009-04-25 20:15 ` Christian Stroetmann OntoLab
2009-04-25 21:04 ` Alli Quaknaa
2009-04-25 23:18 ` Christian Stroetmann OntoLab
2009-04-25 23:52 ` Mat
2009-04-26 8:53 ` Christian Stroetmann OntoLab
2009-04-25 0:03 ` Christian Stroetmann OntoLab
[not found] ` <200904250235.52257.volkerarmin@googlemail.com>
2009-04-25 0:49 ` Christian Stroetmann OntoLab
2009-04-24 23:58 ` Christian Stroetmann OntoLab
2009-04-25 0:25 ` Volker Armin Hemmann
2009-04-25 0:33 ` Christian Stroetmann OntoLab
2009-04-26 11:03 ` Alexander Lyamin
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=49EC17A2.2060203@ontolab.com \
--to=stroetmann@ontolab.com \
--cc=afreije@inn.nl \
--cc=reiserfs-devel@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).