public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: devzero@web.de, linux-kernel@vger.kernel.org
Subject: Re: Reiser @ wired.com
Date: Mon, 09 Jul 2007 14:24:54 -0400	[thread overview]
Message-ID: <46927D76.5070609@tmr.com> (raw)
In-Reply-To: <20070706075741.GW21478@ftp.linux.org.uk>

Al Viro wrote:
> On Fri, Jul 06, 2007 at 09:42:52AM +0200, devzero@web.de wrote:
>> Hi !
>>
>> it seems that it hasn`t brought up here yet, so I`d like to let you know that there is some long Reiser-Story at WIRED MAGAZINE: ISSUE 15.07.
>>
>> For all you gossip fans ;) or for those who want to have some more "in depth" information obout the incident or the person Hans Reiser himself - it`s at:
>>
>> http://www.wired.com/techbiz/people/magazine/15-07/ff_hansreiser
>>
>> scary.....
>> nearly sounds like stuff for a movie for me......
> 
> GAFL.  "Gossip fans" are over there at splashsnot; now bugger off and do not
> crosspost.

It was not too smart to call it gossip, but it certainly does impact 
thinking on including  Reiser4 code in mainline or using it as a patch.

Slashdot is a useful source of links with context, not a primary source 
of information, disregarding information from them is as poor a choice 
as confusing context with the complete information and taking it as gospel.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

  reply	other threads:[~2007-07-09 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06  7:42 Reiser @ wired.com devzero
2007-07-06  7:57 ` Al Viro
2007-07-09 18:24   ` Bill Davidsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-06  8:25 devzero
2007-07-06  9:20 ` Jim van Wel

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=46927D76.5070609@tmr.com \
    --to=davidsen@tmr.com \
    --cc=devzero@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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