All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Vladimir Saveliev <vs@namesys.com>
Cc: redeeman@metanurb.dk, Reiserfs Mailinglist <reiserfs-list@namesys.com>
Subject: Re: hmm, dependencies
Date: Mon, 20 Dec 2004 09:14:28 -0800	[thread overview]
Message-ID: <41C70874.9030001@namesys.com> (raw)
In-Reply-To: <1103308669.3589.117.camel@tribesman.namesys.com>

Vladimir Saveliev wrote:

>Hello
>
>On Fri, 2004-12-17 at 21:09, Redeeman wrote:
>  
>
>>On Fri, 2004-12-17 at 20:30 +0300, Vladimir Saveliev wrote:
>>    
>>
>>>Hello
>>>
>>>On Fri, 2004-12-17 at 18:22, Redeeman wrote:
>>>      
>>>
>>>>On Fri, 2004-12-17 at 16:55 +0300, Vladimir Saveliev wrote:
>>>>        
>>>>
>>>>>Hello
>>>>>
>>>>>On Thu, 2004-12-16 at 22:56, Redeeman wrote:
>>>>>          
>>>>>
>>>>>>hello.. reiser4 is now in mm, but i realize that nearly all of the stuff
>>>>>>that was mm specific when the move to mm was made, are probably merged
>>>>>>into upstream by now, i wonder, can anyone tell me exactly what from mm
>>>>>>it depends on?
>>>>>>
>>>>>>thanks
>>>>>>
>>>>>>            
>>>>>>
>>>>>reiser4 got included into mm not because it needed something of it, but
>>>>>rather because it is supposed that being in mm for certain amount of
>>>>>time reiser4 will get a lot of testing and will prove that it is worth
>>>>>to get included into stock kernel. 
>>>>>          
>>>>>
>>>>im aware, however, the reiser4 patches in mm are against mm, which means
>>>>it depends on something from it, and i'd like to find out what :D so
>>>>that i can take it out and apply to vanilla along with reiser4
>>>>        
>>>>
>>>did you see ftp.namesys.com/pub/reiser4-for-2.6/2.6.9?
>>>It contains all things which reiser4 depends on.
>>>      
>>>
>>nice
>>    
>>
>>>If you would like to add reiser4 to vanilla kernel yourself you would
>>>have to add reiser4 patches of mm kernel to vanilla one:
>>>
>>>people/akpm/patches/2.6/2.6.X/2.6.X-mmY/broken-out/reiser4-*
>>>and add the patch i am attaching to this email.
>>>
>>>      
>>>
>>yeah i tried that, however they dont patch against latest vanilla, it
>>would seem the vfs has changed abit.. i just wondered if anyone knew
>>exactly which of the mm patches was needed to make up for this, but, now
>>you gave me that url :) never mind..
>>
>>    
>>
>
>Ah, yes, you are right, there is a patch which rejects.
>But, I guess that if we keep ftp.namesys.com/pub/reiser4-for-2.6/
>uptodate - that would be ok and we would not have to release separate
>patches for vanilla kernel
>  
>
How is this a one step install process for users?  Anything that 
diverges from a one step install process is bad with the amount badness 
proportional to the number of steps.  Minimize the badness.

Give the task to vitaly though.

>
>  
>
>>thanks
>>    
>>
>
>
>
>  
>


      reply	other threads:[~2004-12-20 17:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16 19:56 hmm, dependencies Redeeman
2004-12-17 13:55 ` Vladimir Saveliev
2004-12-17 15:22   ` Redeeman
2004-12-17 16:39     ` Cal
2004-12-17 17:30     ` Vladimir Saveliev
2004-12-17 18:09       ` Redeeman
2004-12-17 18:37         ` Vladimir Saveliev
2004-12-20 17:14           ` Hans Reiser [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=41C70874.9030001@namesys.com \
    --to=reiser@namesys.com \
    --cc=redeeman@metanurb.dk \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@namesys.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 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.