All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ralph Ulrich <eulenreich@gmx.de>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: The reiser4 programming style is recursive?
Date: Thu, 11 Dec 2008 19:57:31 +0300	[thread overview]
Message-ID: <4941467B.30308@gmail.com> (raw)
In-Reply-To: <49405D98.7000402@gmx.de>

Ralph Ulrich wrote:
> Edward Shishkin schrieb:
>   
>> AFAIK they were unhappy with assertions and "coding nits"  like
>> if (foo) {         bar(); }
>>     
> ....
>   
>> Eventually akpm said that assertions are okay and guys send
>> cleanup patches against other issues once in a while.
>>     
>
> And what are Your plans to get reiser4 in the kernel now!
>   

I wouldn't force the events:
there is no hurry, business plans, timelines, etc..

> As of now it seems that brtfs,
> which has nearly the same "hardware" logic as reiser4
> but lacks the whole ground breaking philosophy,
> will get there first!
>   

And what? I don't see any problems if someone gets it prior
to reiser4.

> Edward, we are all waiting, what do you need for help?
>   

To maintain at least one reiser4 subsystem would be real help..
However, it requires a victim in the person of some student(s),
who is ready to kill the best years by sitting in front of monitor
and studying reiser4 sources..
Do you know such ones? ;)

Edward.

  reply	other threads:[~2008-12-11 16:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 21:34 The reiser4 programming style is recursive? Ralph Ulrich
2008-12-10 21:41 ` Teran McKinney
2008-12-10 22:07   ` Ralph Ulrich
2008-12-10 22:21     ` David Backeberg
2008-12-11  0:09       ` Ralph Ulrich
2008-12-11  4:49     ` Toby Thain
2008-12-10 22:23 ` Edward Shishkin
2008-12-11  0:23   ` Ralph Ulrich
2008-12-11 16:57     ` Edward Shishkin [this message]
2008-12-11 17:37       ` Ralph Ulrich
2008-12-11 18:12         ` Edward Shishkin
2008-12-11 19:05           ` Ralph
2008-12-11 22:56             ` Edward Shishkin
2008-12-12 16:21               ` Ralph
2008-12-13 19:30                 ` Edward Shishkin
2008-12-14 15:24                   ` The... reiser4 with no ambiguity Ralph Ulrich
2008-12-14 19:17                     ` Edward Shishkin
2008-12-16  0:59                       ` Ralph Ulrich
2008-12-17 21:49                         ` Edward Shishkin
2008-12-18 12:28                           ` Ralph Ulrich
2008-12-21 13:38                             ` Edward Shishkin
2008-12-11  0:46   ` The reiser4 .... why it is the future Ralph Ulrich
2008-12-11 11:35     ` The reiser4 .... what it really means Ralph Ulrich
2008-12-11 12:22       ` Ralph Ulrich
2008-12-11 14:36         ` Alexander Lyamin
2008-12-11 17:11           ` The reiser4 ....SDK for experiments outside kernel Ralph
2008-12-11 19:10             ` Edward Shishkin
2008-12-11 19:56               ` Ralph
2008-12-11 23:03                 ` Edward Shishkin
2008-12-11 23:04                 ` Christian Stroetmann OntoLab
2008-12-12  0:54                   ` Ralph
2008-12-11 14:56       ` The reiser4 .... what it really means Christian Stroetmann OntoLab
  -- strict thread matches above, loose matches on Subject: below --
2008-12-12 16:48 The reiser4 programming style is recursive? Mat

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=4941467B.30308@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=eulenreich@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.