From: Hans Reiser <reiser@namesys.com>
To: Jonathan Briggs <jbriggs@esoft.com>
Cc: redeeman@metanurb.dk,
Reiserfs Mailinglist <reiserfs-list@namesys.com>,
Clifford Beshers <clifford.beshers@lindows.com>,
Vladimir Saveliev <vs@namesys.com>,
Alexander Zarochentcev <zam@namesys.com>
Subject: Re: Latest reiser4 snapshot for vanilla/-cko kernel
Date: Thu, 17 Jun 2004 10:22:46 -0700 [thread overview]
Message-ID: <40D1D366.3040107@namesys.com> (raw)
In-Reply-To: <1087489782.3394.0.camel@localhost.localdomain>
Jonathan Briggs wrote:
>On Thu, 2004-06-17 at 09:32, Redeeman wrote:
>
>
>>On Wed, 2004-06-16 at 23:45, Piotr Neuman wrote:
>>
>>
>>>Hi, I took reiser4-2004.06.16-19.36-linux-2.6.7-rc3-mm1.diff.gz from
>>>http://namesys.com/auto-snapshots/ and it appeared to apply pretty well on
>>>vanilla 2.6.7 kernel. So I made patches for vanilla and -cko available in:
>>>
>>>http://kem.p.lodz.pl/~peter/cko/reiser4/
>>>
>>>Hope those patches work ok :).
>>>
>>>
>>have you tried it? afaik reiser4 will apply clean on vanilla, however, i
>>think the internal changes in the kernel disallows reiser4 to run
>>
>>
>>>BTW great kudos to reiser4 team...
>>>
>>>
>
>Piotr's patches are working fine for me. Kernel 2.6.7 (vanilla) and
>Reiser4 seem happy together.
>
>
zam, please describe what bugs are outstanding (better than vs did).
next prev parent reply other threads:[~2004-06-17 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 21:45 Latest reiser4 snapshot for vanilla/-cko kernel Piotr Neuman
2004-06-17 15:32 ` Redeeman
2004-06-17 16:29 ` Jonathan Briggs
2004-06-17 17:22 ` Hans Reiser [this message]
2004-06-18 19:44 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2004-06-18 22:22 David Dabbs
2004-06-19 21:58 ` mjt
2004-06-18 22:27 David Dabbs
2004-07-07 22:03 Piotr Neuman
2004-07-08 6:54 ` mjt
2004-07-08 8:09 ` Hans Reiser
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=40D1D366.3040107@namesys.com \
--to=reiser@namesys.com \
--cc=clifford.beshers@lindows.com \
--cc=jbriggs@esoft.com \
--cc=redeeman@metanurb.dk \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.com \
--cc=zam@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.