All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Namesys.COM>
To: Reiserfs mail-list <Reiserfs-List@Namesys.COM>,
	Reiserfs developers mail-list <Reiserfs-Dev@Namesys.COM>
Subject: reiser4 snapshot
Date: Tue, 23 Dec 2003 14:11:33 +0300	[thread overview]
Message-ID: <16360.8933.883691.281877@laputa.namesys.com> (raw)

Hello,

new reiser4 snapshot (for 2.6.0) is available at the

http://www.namesys.com/snapshots/2003.12.23/

See READ.ME file there for more instructions.

--------------------------------------------------------------------------------
WARNING: WARNING: WARNING: WARNING: WARNING: WARNING: WARNING: WARNING: WARNING:
Don't use Reiser4 in production environments. It is in the debugging stage.

--------------------------------------------------------------------------------
                                    Files:
--------------------------------------------------------------------------------

core.diff                   Modifications to the core part of the kernel
                            necessary for reiser4

reiser4.only.diff.gz        Reiser4 source code as -p1 patch for the kernel
                            source tree, compressed

all.diff.gz                 Above two patches combines and compressed

reiser4.tar.gz              Reiser4 source code. This also contains SCCS data.

broken-out                  core.diff split into separate patches

reiser4progs-0.4.20.tar.gz  reiser4progs: mkfs, fsck, etc.

libaal-0.4.15.tar.gz        libaal library required by reiser4progs

Nikita.

             reply	other threads:[~2003-12-23 11:11 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23 11:11 Nikita Danilov [this message]
2003-12-23 11:16 ` reiser4 snapshot 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
  -- strict thread matches above, loose matches on Subject: below --
2004-08-13 14:23 REISER4 snapshot 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
2004-08-04 18:28 Vladimir V. Saveliev
2004-08-04 18:33 ` Jonathan Briggs
2004-08-04 18:34 ` mjt
2004-08-06  0:06   ` Philippe Gramoullé
2003-08-11 15:57 reiser4 snapshot Nikita Danilov
2003-08-11 16:41 ` 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

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=16360.8933.883691.281877@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.