All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: Oleg Drokin <green@namesys.com>
Cc: reiserfs-list@namesys.com, reiserfs-dev@namesys.com
Subject: Re: New reiser4 snapshot (as of August 22, 2003)
Date: Fri, 22 Aug 2003 18:16:35 -0700	[thread overview]
Message-ID: <3F46C073.4080008@tupshin.com> (raw)
In-Reply-To: <20030822150853.GA960@namesys.com>

Oleg Drokin wrote:

>Hello!
>
>   I have just released new snapshot of reiser4.
>   Release notes follows.
>   Give it a try.
>
>Reiser4 snapshot for 2003.08.22
>
>WARNING!!! This code is experimental! WE ARE NOT KIDDING! DO NOT PUT
>ANY VALUABLE DATA ON REISER4 YET!
>
>Fixed builds for 64bit arches (there are still some warnings, but it
>should work now, I hope). Fixed some bugs.
>There are still some stability problems on SMP machines that we are working on.
>
>If you used reiser4progs from last snapshot (August 11th), you need to upgrade those
>to fix critical largekeys bug in mkfs.reiser4
>
>Snapshot is released as a patch against linux-2.6.0-test3-bk9.
>REISER4_NOOPT config option (Disable compiler optimizations for reiser4 code.)
>is known to not compile on x86.
>Enable CONFIG_REISER4_LARGE_KEY, as reiser4progs are creating filesystems with
>large keys by default.
>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
>
Are these patches available outside of bitkeeper, and if so, where are 
they located?

-Tupshin


  parent reply	other threads:[~2003-08-23  1:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-22 15:08 New reiser4 snapshot (as of August 22, 2003) Oleg Drokin
2003-08-22 17:52 ` David Nielsen
2003-08-22 17:57   ` Nikita Danilov
2003-08-22 18:08     ` David Nielsen
2003-08-22 18:12       ` Nikita Danilov
2003-08-22 23:47         ` David Nielsen
2003-08-23  0:15           ` Christophe Saout
2003-08-23  0:25           ` Vince
2003-08-23  0:29             ` David Nielsen
2003-08-23  3:38             ` Boris Tschirschwitz
2003-08-23  1:57           ` Hans Reiser
2003-08-23  1:16 ` Tupshin Harper [this message]
2003-08-23  3:07   ` Jürgen Botz
2003-08-23  7:39   ` Oleg Drokin
2003-08-23  8:06 ` David Nielsen

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=3F46C073.4080008@tupshin.com \
    --to=tupshin@tupshin.com \
    --cc=green@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.