From: Jeff Garzik <jgarzik@pobox.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>,
Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: [ANNOUNCE]: reiser4
Date: Tue, 29 Oct 2002 13:22:00 -0500 [thread overview]
Message-ID: <3DBED1C8.5080404@pobox.com> (raw)
In-Reply-To: 15806.51536.985203.709475@laputa.namesys.com
Nikita Danilov wrote:
>Hello,
>
>Snapshot of reiser4 source code can be found at
>http://www.namesys.com/snapshots/2002.10.29/.
>
>It is set of patches against current Linus BK tree (2.5.44).
>
>
The current Linus BK tree is quite a bit different from 2.5.44 ;-)
Take a look at 2.5.44-bk1 at
ftp://ftp.kernel.org/pub/linux/kernel/v2.5/snapshots/
A -bk2 snapshot should appear within the hour, too, with heaps of
additional changes.
Jeff
next prev parent reply other threads:[~2002-10-29 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 17:45 [ANNOUNCE]: reiser4 Nikita Danilov
2002-10-29 18:22 ` Jeff Garzik [this message]
2002-10-29 18:39 ` Nikita Danilov
2002-10-30 16:22 ` Tomas Szepe
2002-10-30 16:29 ` Nikita Danilov
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=3DBED1C8.5080404@pobox.com \
--to=jgarzik@pobox.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=Nikita@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox