All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Namesys.COM>
To: Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Cc: Reiserfs developers mail-list <Reiserfs-Dev@Namesys.COM>
Subject: reiser4 snapshot
Date: Mon, 11 Aug 2003 19:57:31 +0400	[thread overview]
Message-ID: <16183.48363.884605.564937@laputa.namesys.com> (raw)

Hello,

new reiser4 snapshot is available at 

http://thebsh.namesys.com/snapshots/2003.08.11/

**********************************************************************
                              WARNING!!! 
                      This code is experimental! 
    WE ARE NOT KIDDING! DO NOT PUT ANY VALUABLE DATA ON REISER4 YET!
**********************************************************************

Lots of changes in this snapshot compared to previous one that was
release over half of year ago.  Everything should be better and more
stable I hope.

Snapshot is released as a patch against linux-2.6.0-test3.

REISER4_NOOPT config option (Disable compiler optimizations for reiser4
code.)  is known to not compile on x86.

The reiser4-kernelonly.diff file represents only required kernel
modifications if you plan to use our reiser4 bk repository. It does not
contains any reiser4 code

The reiser4.diff is full patch with everything included.

With this snapshot reiser4 supports different on-disk format by default,
so you should recreate your reiser4 file systems.

Nikita.


             reply	other threads:[~2003-08-11 15:57 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11 15:57 Nikita Danilov [this message]
2003-08-11 16:41 ` reiser4 snapshot Carl-Daniel Hailfinger
2003-08-11 16:55   ` Nikita Danilov
2003-08-12  0:32 ` Boris Tschirschwitz
2003-08-12  6:05   ` Oleg Drokin
2003-08-12  7:22     ` Cyrille Chepelov
2003-08-12  7:31       ` Yury Umanets
2003-08-12  8:02         ` Cyrille Chepelov
2003-08-12  8:05           ` Vitaly Fertman
2003-08-12  8:25           ` Yury Umanets
2003-08-12  9:48             ` Cyrille Chepelov
2003-08-12  9:54               ` Yury Umanets
2003-08-12 10:42                 ` Yury Umanets
2003-08-12 11:44                 ` Cyrille Chepelov
2003-08-12 11:44                   ` Yury Umanets
2003-08-12  7:41       ` Yury Umanets
2003-08-13 16:34     ` Boris Tschirschwitz
2003-08-12  8:28 ` Henning Westerholt
2003-08-12  8:56   ` Nikita Danilov
2003-08-12  9:18     ` Henning Westerholt
2003-08-12  9:27   ` Oleg Drokin
  -- strict thread matches above, loose matches on Subject: below --
2003-12-23 11:11 Nikita Danilov
2003-12-23 11:16 ` Carl-Daniel Hailfinger
2003-12-23 11:26   ` Nikita Danilov
2003-12-23 12:22 ` Viktors Rotanovs
2003-12-23 12:31   ` Nikita Danilov
2003-12-23 13:02     ` Viktors Rotanovs
2003-12-23 13:07       ` Nikita Danilov
2004-08-04 18:28 REISER4 snapshot Vladimir V. Saveliev
2004-08-04 18:33 ` Jonathan Briggs
2004-08-04 18:34 ` mjt
2004-08-06  0:06   ` Philippe Gramoullé
2004-08-13 14:23 Vladimir V. Saveliev
2004-08-13 14:36 ` Domenico Andreoli
2004-08-13 14:38   ` Vladimir V. Saveliev
2004-08-13 14:45     ` Stefan Schweizer
2004-08-13 14:50       ` Vladimir V. Saveliev
2004-08-13 15:02 ` Domenico Andreoli
2004-08-13 15:11   ` Vladimir V. Saveliev
2004-08-13 15:14   ` Nikita Danilov
2004-08-13 15:20     ` Domenico Andreoli

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=16183.48363.884605.564937@laputa.namesys.com \
    --to=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.