All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ookhoi <ookhoi@humilis.net>
To: Nikita Danilov <Nikita@namesys.com>
Cc: Reiserfs mail-list <Reiserfs-List@namesys.com>,
	Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>
Subject: Re: [ANNOUNCE]: reiser4 snapshot
Date: Thu, 16 Jan 2003 09:14:20 +0100	[thread overview]
Message-ID: <20030116091420.G7526@humilis> (raw)
In-Reply-To: <15880.36350.410391.708308@laputa.namesys.com>

Nikita Danilov wrote (ao):
> new reiser4 snapshot is available at:
> 
> http://www.namesys.com/snapshots/2002.12.24/
> 
> It is released as a patch against linux-2.5.53 kernel. It should also
> work with current (December 24th) bk snapshot at
> http://linux.bkbits.net/linux-2.5
> 
> This is mostly bug fixing release.
> 
> READ.ME file contains changelog.
> 
> In addition, our public BK repository with reiser4 code is available
> at bk://namesys.com/bk/reiser4.

Hi Nikita,

Is there also a BK repository with the reiserfs4-progs?

And what is the right way to integrate reiser4 into the kernel? At the
moment I pull reiser4 and linux-2.5, patch linux-2.5 with the
reiser4.diff out of the snapshots dir, and replace fs/reiser4 with the
BK reiser4. 

This works*, but I think the patch part is not the right way.

* I can compile a 2.5 kernel, boot it, and mkfs.reiser4 a partition.

Thanks in advance!

  reply	other threads:[~2003-01-16  8:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-24 16:40 [ANNOUNCE]: reiser4 snapshot Nikita Danilov
2003-01-16  8:14 ` Ookhoi [this message]
2003-01-16  8:22   ` [reiserfs-dev] " Oleg Drokin
2003-01-16  8:31     ` Ookhoi
  -- strict thread matches above, loose matches on Subject: below --
2003-02-13 14:44 Nikita Danilov
2003-02-13 19:32 ` Ookhoi
2003-02-14  6:53   ` Oleg Drokin
2003-01-17 10:33 Nikita Danilov
2003-01-17 12:09 ` Ookhoi
2003-01-17 12:11   ` Ookhoi
2002-11-20 10:30 Nikita Danilov
2002-11-12 15:42 Nikita Danilov
2002-11-12 15:48 ` Nikita Danilov
2002-11-13  8:14 ` Todd Lyons

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=20030116091420.G7526@humilis \
    --to=ookhoi@humilis.net \
    --cc=Nikita@namesys.com \
    --cc=Reiserfs-Dev@namesys.com \
    --cc=Reiserfs-List@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.