From: Edward Shishkin <edward.shishkin@gmail.com>
To: intelfx@intelfx.name,
ReiserFS development mailing list
<reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4 Upstream Git Repositories on GitHub
Date: Tue, 27 Sep 2016 00:37:33 +0200 [thread overview]
Message-ID: <57E9A32D.3000108@gmail.com> (raw)
In-Reply-To: <1474927548.10826.6.camel@intelfx.name>
On 09/27/2016 12:05 AM, Ivan Shapovalov wrote:
> On 2016-09-24 at 22:16 +0200, Edward Shishkin wrote:
>> Hello everyone,
>>
>> I have set up the updated Namesys repositories at my Github page.
>> Those repositories are supposed to contain the latest updates in
>> the (stable) master branch and in other (experimental) branches that
>> I'll announce.
>>
>> 1) https://github.com/edward6/reiser4
>>
>> This is a "standalone" reiser4 tree, which doesn't include specific
>> changes of Linux kernel needed for reiser4 port. Such changes can be
>> found at the project's page on Sourceforge:
>> https://sourceforge.net/projects/reiser4/
>>
>> An example of work with the standalone reiser4 tree:
>>
>> . Patch the respective kernel with the latest available stuff from
>> Sourceforge;
>> . cd to the "fs" directory;
>> . delete the directory reiser4;
>> . instead of the deleted stuff clone the standalone reiser4
>> repository from Github;
>> . build and install as usual.
>>
>> 2) Libaal and Reiser4progs:
>>
>> https://github.com/edward6/libaal
>> https://github.com/edward6/reiser4progs
>>
>> Before building Libaal and Reiser4progs execute the ./prepare script,
>> which will create files needed for build process.
>>
>> Thanks,
>> Edward.
> Wow, finally.
>
> Maybe we could avoid that "all changes for 10 years" commit?
Hi Ivan,
Sorry, don't have a time to granulate it.
> I tried to keep track of all patches since 3.2...
There will be "all changes for 6 years" commit.
Is it much better?
next prev parent reply other threads:[~2016-09-26 22:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 20:16 Reiser4 Upstream Git Repositories on GitHub Edward Shishkin
2016-09-25 0:36 ` Christian Kujau
2016-09-26 22:05 ` Ivan Shapovalov
2016-09-26 22:37 ` Edward Shishkin [this message]
2016-09-26 23:03 ` Ivan Shapovalov
2016-09-27 1:43 ` Ivan Shapovalov
2016-09-27 14:04 ` Edward Shishkin
2016-09-27 2:43 ` Ivan Shapovalov
2016-09-27 14:13 ` Edward Shishkin
2016-09-27 18:36 ` Ivan Shapovalov
2016-09-27 21:47 ` Edward Shishkin
2016-09-27 21:51 ` Ivan Shapovalov
2016-09-28 10:17 ` Edward Shishkin
2016-09-28 10:36 ` Ivan Shapovalov
2016-09-28 13:56 ` Edward Shishkin
2016-09-28 14:44 ` Edward Shishkin
2016-09-28 15:03 ` Ivan Shapovalov
2016-09-28 19:58 ` Edward Shishkin
2016-09-28 21:50 ` Ivan Shapovalov
2016-09-29 15:07 ` Edward Shishkin
2016-09-30 3:28 ` Ivan Shapovalov
2016-10-04 15:52 ` Edward Shishkin
2016-09-30 6:56 ` Ivan Shapovalov
2016-10-03 14:33 ` Edward Shishkin
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=57E9A32D.3000108@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=intelfx@intelfx.name \
--cc=reiserfs-devel@vger.kernel.org \
/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.