From: Nikita Danilov <Nikita@Namesys.COM>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>,
Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: [ANNOUNCE]: reiser4
Date: Wed, 30 Oct 2002 19:29:32 +0300 [thread overview]
Message-ID: <15808.2284.23607.625639@laputa.namesys.com> (raw)
In-Reply-To: <20021030162200.GD1995@louise.pinerecords.com>
Tomas Szepe writes:
> > > 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.
> > >
> >
> > Sorry, my fault.
> >
> > Patches in reiser4 snapshot are against Linus BK repository at
> > http://linux.bkbits.net/linux-2.5. Numbers 2, 5, and 44, are, of course,
> > just VERSION, PATCHLEVEL, and SUBLEVEL in the Makefile of the said
> > repository.
>
> The following is needed to compile reiser4 in 2.5.44-bk3:
Thanks a lot.
>
> diff -urN linux-2.5.44-bk3-reiser4/mm/Makefile linux-2.5.44-bk3-reiser4.1/mm/Makefile
> --- linux-2.5.44-bk3-reiser4/mm/Makefile 2002-10-12 13:35:03.000000000 +0200
> +++ linux-2.5.44-bk3-reiser4.1/mm/Makefile 2002-10-30 17:15:10.000000000 +0100
> @@ -2,7 +2,7 @@
> # Makefile for the linux memory manager.
> #
>
Nikita.
prev parent reply other threads:[~2002-10-30 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 17:45 Nikita Danilov
2002-10-29 18:22 ` Jeff Garzik
2002-10-29 18:39 ` Nikita Danilov
2002-10-30 16:22 ` Tomas Szepe
2002-10-30 16:29 ` Nikita Danilov [this message]
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=15808.2284.23607.625639@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=Reiserfs-List@Namesys.COM \
--cc=jgarzik@pobox.com \
--cc=szepe@pinerecords.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
Powered by JetHome