From: James Blackwell <jblack@linuxguru.net>
To: linux-kernel@vger.kernel.org
Cc: reiser@namesys.com (Hans Reiser)
Subject: Re: Listmaster request: Do not blacklist rms@gnu.org
Date: Tue, 22 Oct 2002 13:50:01 -0400 [thread overview]
Message-ID: <E1843AH-0001D2-00@comet.linuxguru.net> (raw)
In-Reply-To: <3DB555D5.7090904@namesys.com>
In lists.linux.kernel.development, you wrote:
> James Blackwell wrote:
>
>>Do you think Hans Reiser
>>felt like you were doing the right thing when he had to change his
>>timeline on Reiserfs so as to avoid competing with your project as long
>>as possible?
>>
>>
>>
> I did not change my timeline. Though I was tempted to move version
> control up in the priority queue, it nonetheless will remain low until
> the right developer comes along, or other things that also need doing
> are moved out of that queue.
I'm very sorry. I could have sworn you had said something along the
lines of 'Some day I want to put version control into reiser, which
could technically be considered a competitor to bitkeeper. I have a lot
of other things to do with reiserfs as well so I'll do those first'. But
when I went back through the list, I couldn't find it.
The closest to that I could find was the following:
> reiser4 will not contain version control. I don't know when version
> control will go into ReiserFS. I do think it should go in eventually
> though, as it makes distributed filesystems more effective if there is
> version control functionality. We would do something that in no way
> resembled BK. We would do it after implementing the core distributed
> tree algorithms. Probably not going to happen in less than 3-5 years.
> ...
> There are so many features missing from ReiserFS, and I am not really
> picky about what order they go in..... With Reiser4 we finally have
I must have gotten the issues involved with reiserfs confused with
another project.
Again, I'm sorry I got your position wrong.
--
GnuPG fingerprint AAE4 8C76 58DA 5902 761D 247A 8A55 DA73 0635 7400
James Blackwell -- Director http://www.linuxguru.net
next prev parent reply other threads:[~2002-10-22 17:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 17:27 Listmaster request: Blacklist rms@gnu.org Christoph Hellwig
2002-10-21 17:44 ` Jon Portnoy
2002-10-21 17:57 ` Roman Zippel
2002-10-21 18:02 ` Christoph Hellwig
2002-10-21 18:16 ` Roman Zippel
2002-10-21 18:32 ` Christoph Hellwig
2002-10-21 18:58 ` Roman Zippel
2002-10-21 19:02 ` Christoph Hellwig
2002-10-21 19:23 ` Roman Zippel
2002-10-22 1:15 ` Rob Landley
2002-10-21 18:02 ` Alan Cox
2002-10-21 17:51 ` Christoph Hellwig
2002-10-21 18:28 ` Matti Aarnio
2002-10-21 18:33 ` Jason Williams
[not found] ` <20021021190244.GB21851@compsoc.man.ac.uk>
2002-10-21 19:23 ` Jason Williams
2002-10-21 21:51 ` DervishD
2002-10-22 1:40 ` Murray J. Root
2002-10-22 1:49 ` Listmaster request: Do not blacklist rms@gnu.org Jeff Garzik
2002-10-22 2:13 ` Andrew Morton
2002-10-22 2:31 ` Larry McVoy
2002-10-22 6:19 ` James Blackwell
2002-10-22 13:42 ` Hans Reiser
2002-10-22 17:50 ` James Blackwell [this message]
2002-10-22 15:00 ` Larry McVoy
2002-10-22 17:24 ` James Blackwell
2002-10-22 17:42 ` Christoph Hellwig
2002-10-22 18:12 ` James Blackwell
2002-10-22 18:15 ` Justin Guyett
2002-10-22 17:44 ` Larry McVoy
2002-10-22 17:46 ` Christoph Hellwig
2002-10-22 18:06 ` Roman Zippel
2002-10-22 18:09 ` Christoph Hellwig
2002-10-22 18:27 ` Christoph Hellwig
2002-10-22 18:06 ` Gerhard Mack
2002-10-22 1:51 ` Listmaster request: Blacklist rms@gnu.org Larry McVoy
2002-10-22 1:56 ` John Jasen
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=E1843AH-0001D2-00@comet.linuxguru.net \
--to=jblack@linuxguru.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@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
Powered by JetHome