From: Alexey Dobriyan <adobriyan@gmail.com>
To: Ed Tomlinson <tomlins@cam.org>
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>,
Hans Reiser <reiser@namesys.com>,
Ed Cogburn <edcogburn@hotpop.com>,
linux-kernel@vger.kernel.org
Subject: Re: reiser4 vs politics: linux misses out again
Date: Sun, 10 Jul 2005 20:06:26 +0400 [thread overview]
Message-ID: <200507102006.27152.adobriyan@gmail.com> (raw)
In-Reply-To: <200507100848.05090.tomlins@cam.org>
On Sunday 10 July 2005 16:48, Ed Tomlinson wrote:
> On Sunday 10 July 2005 01:10, Horst von Brand wrote:
> > Ed Cogburn <edcogburn@hotpop.com> wrote:
> > > David Lang wrote:
> > > > On Fri, 8 Jul 2005, Ed Tomlinson wrote:
> >
> > > >> No Flame from me. One thing to remember is that Hans and friends
> > > >> _have_ supported R3 for years.
> >
> > They let it fall into disrepair when they started work on 4.
> >
> > > >> This is an undisputed fact.
> >
> > Exactly.
>
> This is FUD. Hans do you have figures on how many fixes for R3 have
> been added in the last year or so?
You don't need Hans to find out how many. linux.bkbits.net is still online.
http://linux.bkbits.net:8080/linux-2.6/src/fs/reiserfs?nav=index.html|src/|src/fs
next prev parent reply other threads:[~2005-07-10 15:59 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 12:26 reiser4 vs politics: linux misses out again shevek
2005-06-30 9:44 ` Christopher Warner
2005-06-30 12:45 ` Rik Van Riel
2005-06-30 12:53 ` Richard B. Johnson
2005-06-30 20:21 ` Bill Davidsen
2005-07-01 20:54 ` James Courtier-Dutton
2005-06-30 15:33 ` Jim Crilly
2005-06-30 16:02 ` Markus Törnqvist
2005-06-30 18:10 ` Jim Crilly
2005-07-02 13:05 ` Ed Cogburn
2005-07-02 14:59 ` Christoph Hellwig
2005-07-03 22:34 ` Ed Cogburn
2005-07-02 21:56 ` Jim Crilly
2005-07-03 23:30 ` Ed Cogburn
2005-07-04 1:13 ` Jim Crilly
2005-07-04 1:25 ` Ed Cogburn
2005-07-04 2:11 ` Horst von Brand
2005-07-05 19:44 ` cutaway
2005-07-08 22:59 ` Ed Cogburn
2005-07-09 0:26 ` Ed Tomlinson
2005-07-09 0:39 ` David Lang
2005-07-09 3:25 ` Ed Cogburn
2005-07-09 21:40 ` David Lang
2005-07-10 5:10 ` Horst von Brand
2005-07-10 12:48 ` Ed Tomlinson
2005-07-10 16:06 ` Alexey Dobriyan [this message]
2005-07-10 20:21 ` Jim Crilly
2005-07-11 0:01 ` Ed Cogburn
2005-07-11 0:13 ` David Lang
2005-07-11 0:18 ` Jim Crilly
2005-07-11 2:43 ` Ed Cogburn
2005-07-11 2:40 ` Jim Crilly
2005-07-11 11:09 ` Ed Tomlinson
2005-07-11 18:16 ` Jim Crilly
2005-07-11 19:07 ` Hans Reiser
2005-07-11 1:12 ` Hans Reiser
2005-07-11 9:01 ` Erik Hensema
2005-07-11 18:15 ` Horst von Brand
2005-07-11 19:04 ` Hans Reiser
2005-07-11 20:40 ` Erik Hensema
2005-07-09 7:23 ` Hans Reiser
2005-07-04 6:50 ` Jens Axboe
2005-07-04 13:42 ` Maciej Soltysiak
2005-07-04 1:35 ` Horst von Brand
2005-07-01 4:08 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2005-06-30 15:27 Markus Törnqvist
2005-06-30 22:37 Parag Warudkar
2005-07-01 11:29 ` Richard B. Johnson
2005-07-01 11:43 ` Luigi Genoni
2005-07-01 12:17 ` Richard B. Johnson
2005-07-01 12:30 ` Luigi Genoni
2005-07-01 15:27 arjun kumar
2005-07-01 15:44 ` Artem B. Bityuckiy
2005-07-01 15:55 ` Schneelocke
2005-07-01 15:59 ` arjun kumar
2005-07-01 15:53 Parag Warudkar
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=200507102006.27152.adobriyan@gmail.com \
--to=adobriyan@gmail.com \
--cc=edcogburn@hotpop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=tomlins@cam.org \
--cc=vonbrand@inf.utfsm.cl \
/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