From: Edward Shishkin <edward.shishkin@gmail.com>
To: Markus <mp.lists@free.fr>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: "Home" of reiser4?
Date: Mon, 21 May 2012 19:41:09 +0200 [thread overview]
Message-ID: <4FBA7E35.7000008@gmail.com> (raw)
In-Reply-To: <4FBA783F.1060801@gmail.com>
On 05/21/2012 07:15 PM, Edward Shishkin wrote:
> On 05/21/2012 06:47 PM, Markus wrote:
>> Hello Edward, Glenn, Viji, Sandro and all other activists,
>>
>
> Hello.
>
>> now, that the patches are gone from
>> http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/,
>> is http://sourceforge.net/projects/reiser4/ now the "official" home
>> for further reiser4 development?
>
> Yes.
>
>>
>> To which degree is this platform intended to be used {documentation,
>> discussions,
Developers documentation has been performed as a set
of comments in reiser4 source code.
Some info ("getting started", etc.) can be found here:
https://reiser4.wiki.kernel.org/index.php/Main_Page
And all discussions are going here (in the mailing list).
Thanks,
Edward.
versioned sources, bug tracking}?
>
> Patches and (maybe) SCM.
>
> I don't see a need to track bugs of current stuff:
> any problems are resolved to the old 2-3 bugs that
> I am aware of..
>
>>
>> Are older patchsets {eg. those still on
>> http://130.83.2.34/pub/linux/mirrors/misc/old/reiserfs/reiser4-for-2.6
>> and
>> http://ftp.sunet.se/pub/Linux/kernels/people/edward/reiser4/reiser4-for-2.6/}
>>
>> intended to be kept on Sourceforge as well?
>
> Good idea..
>
>>
>> Any ideas about authorisation {who may write what}?
>
> Me. And other active reiser4 developers (if any)..
>
> Thanks,
> Edward.
next prev parent reply other threads:[~2012-05-21 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 16:47 "Home" of reiser4? Markus
2012-05-21 17:15 ` Edward Shishkin
2012-05-21 17:41 ` Edward Shishkin [this message]
2012-05-21 23:39 ` Markus
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=4FBA7E35.7000008@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=mp.lists@free.fr \
--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.