public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ryan Hope <rmh3093@gmail.com>
Cc: Theodore Tso <tytso@mit.edu>, Ric Wheeler <ricwheeler@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Reiserfs mailing list <reiserfs-devel@vger.kernel.org>
Subject: Re: reiser4 for 2.6.27-rc1
Date: Sun, 03 Aug 2008 02:56:33 +0400	[thread overview]
Message-ID: <4894E621.8090300@gmail.com> (raw)
In-Reply-To: <48f7fe350808020847iff03890nc6d910f7b77fee9e@mail.gmail.com>

Ryan Hope wrote:
> Can you explain a little more what this "plugin design documentation"
> actually is and how it supposed to help?
> -Ryan
>
>   

This document is to define plugins, etc primitives (like conversion
of run-time objects) used in reiser4, and to describe all reiser4
interfaces, so that it will be clear that VFS functionality is not
duplicated, there are not VFS layers inside reiser4, etc. (many items
are devoted to interaction between VFS and reiser4).
I am sorry, but these concepts (which are very central) have not been
worked out carefully enough at the moment of this 3-year-old review:
http://kerneltrap.org/node/5330

Edward.

> On Fri, Aug 1, 2008 at 6:40 PM, Edward Shishkin
> <edward.shishkin@gmail.com> wrote:
>   
>> Ric Wheeler wrote:
>>     
>>> Theodore Tso wrote:
>>>       
>>>> On Fri, Aug 01, 2008 at 12:34:53PM -0400, Ryan Hope wrote:
>>>>
>>>>         
>> Hi, I am here :)
>> Join our mailing list:
>>
>> http://vger.kernel.org/vger-lists.html#reiserfs-devel
>> http://marc.info/?l=reiserfs-devel&r=1&w=2
>>
>> There are many interesting tasks to resolve/investigate..
>>
>>     
>>>>> Hmmm, removing the plugin support might not be so hard....  I might
>>>>> have to try this...
>>>>>           
>> Please, don't try to do this.
>>
>> I am working on the plugin design document. It will be ready
>> approximately in September. I believe that it'll address all the
>> mentioned complaints.
>>
>>     
>>>>> I am not impressed with btrfs yet.
>>>>>
>>>>>           
>>>> Well, if you're going to work on reiser4 (and I think there were other
>>>> people who had also expressed interest/plans to work on it; you might
>>>> try doing a search on the various mailing lists so you can coordinate
>>>> with them and avoid duplicating work), my suggestion to you would be
>>>> to find the comments that were made by the reviewers way back when,
>>>> and make sure those comments have been addressed.
>>>>
>>>> Then, re-requests a code review, and promise that you won't abuse, and
>>>> insult the integrity and impugn the motivations of the reviewers
>>>>         
>> Well, Ted, I'll promise ;)
>> We'll adhere strictly the propositional logic in the review thread..
>>
>> Thanks,
>> Edward.
>>
>>     
>>>> like
>>>> Hans did, and hopefully after they review the code, fix those problems
>>>> as well.  Then you can try resubmitting for inclusion.
>>>>
>>>> Best regards,
>>>>
>>>>                                              - Ted
>>>>
>>>>         
>>> My most up to date information is that Edward is still actively
>>> working on reiser4....
>>>
>>> ric
>>>
>>>
>>>       
>>
>>     
>
>   


  reply	other threads:[~2008-08-02 22:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 13:49 reiser4 for 2.6.27-rc1 Ryan Hope
2008-08-01 16:25 ` Theodore Tso
2008-08-01 16:34   ` Ryan Hope
2008-08-01 16:45     ` Theodore Tso
2008-08-01 18:15       ` Ric Wheeler
2008-08-01 22:40         ` Edward Shishkin
2008-08-02 15:47           ` Ryan Hope
2008-08-02 22:56             ` Edward Shishkin [this message]
2008-08-02 23:18               ` Ryan Hope
2008-08-04 11:11                 ` Edward Shishkin
2008-08-04 11:18                   ` Dushan Tcholich
2008-08-04 11:34                     ` Dushan Tcholich
2008-08-02  2:30   ` Alexey Dobriyan
  -- strict thread matches above, loose matches on Subject: below --
2008-08-04 12:26 Tim Tassonis
2008-08-13 12:58 ` Pavel Machek
2008-08-13 13:18   ` Adrian Bunk
2008-08-13 13:24     ` Michael Krufky
2008-08-13 13:34       ` Adrian Bunk
2008-08-13 13:30         ` Alan Cox
2008-08-13 13:46         ` Michael Krufky
2008-08-13 14:50           ` Frans Meulenbroeks
2008-08-13 23:04         ` Jeremy Fitzhardinge
2008-08-25 20:09           ` Bill Davidsen
2008-08-13 13:37       ` Tim Tassonis
2008-08-13 13:36         ` Alan Cox
2008-08-13 14:00           ` Tim Tassonis
2008-08-13 14:59             ` Ryan Hope
2008-08-13 15:24               ` Tim Tassonis
2008-08-13 16:18                 ` Jeff Chua
2008-08-13 16:30                 ` Ryan Hope
2008-08-25 20:04           ` Bill Davidsen
2008-08-13 13:56     ` Andi Kleen
2008-08-13 14:02       ` Tim Tassonis

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=4894E621.8090300@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=ricwheeler@gmail.com \
    --cc=rmh3093@gmail.com \
    --cc=tytso@mit.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