public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Marc Perkel <marc@perkel.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Arjan van de Ven <arjan@infradead.org>,
	"Hesse, Christian" <mail@earthworm.de>,
	linux-kernel@vger.kernel.org
Subject: Re: So - What's going on with Reiser 4?
Date: Sun, 15 Jan 2006 13:30:20 -0500	[thread overview]
Message-ID: <1137349821.25801.30.camel@mindpipe> (raw)
In-Reply-To: <43CA9050.8080601@perkel.com>

On Sun, 2006-01-15 at 10:11 -0800, Marc Perkel wrote:
> 
> Alan Cox wrote:
> > On Sad, 2006-01-14 at 20:34 -0800, Marc Perkel wrote:
> >   
> >>>> I am not going to search the archives before asking a question.
> >>>>         
> >>>   
> >>>       
> >> I just asked a question. Obviously it's a question that seems to 
> >> politically hot to handle. I didn't realize reiser 4 was a prohibited 
> >> subject.
> >>     
> >
> > Its not. Possibly your behaviour should come under "prohibited attitude"
> > but we don't have thought crime on the list beyond that your government
> > may be seeking to impose.
> >
> > Its an "oh god not again" subject that has been beaten to death
> > repeatedly, and that is why people asked you to look at the archive
> > instead of wasting everyones time.
> >
> > If you are really keen to get resierfs4 into the base kernel why not
> > email the reiserfs4 people and ask to help clean up the code and test
> > it ?
> >
> > Alan
> >   
> Look - all I did was ask a simple question about what was the status of 
> Reiser 4 and everyone is freaking out that I asked the question. You 
> guys are acting like you are members of a cult or something. I'm not 
> advocating anything. I just asked a question.
> 

No one freaked out, we just said "we have no idea, ask the reiser4
developers".

Lee


  reply	other threads:[~2006-01-15 18:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13 23:28 So - What's going on with Reiser 4? Marc Perkel
2006-01-14 11:08 ` Arjan van de Ven
2006-01-14 12:22   ` Hesse, Christian
2006-01-14 12:44     ` Arjan van de Ven
2006-01-15  0:17       ` Marc Perkel
2006-01-15  2:50         ` Lee Revell
2006-01-15  3:23           ` Marc Perkel
2006-01-15  4:25             ` Lee Revell
2006-01-15  4:34               ` Marc Perkel
2006-01-15  8:52                 ` Arjan van de Ven
2006-01-15 15:11                   ` Marc Perkel
2006-01-15 15:21                     ` Arjan van de Ven
2006-01-16  3:24                     ` Kurt Wall
2006-01-16 15:59                       ` Marc Perkel
2006-01-16 20:20                         ` Kurt Wall
2006-01-15 18:09                 ` Alan Cox
2006-01-15 18:11                   ` Marc Perkel
2006-01-15 18:30                     ` Lee Revell [this message]
2006-01-16  2:05                     ` Alan Cox
2006-01-20 12:00               ` Andrew Morton
2006-01-20 13:13                 ` Pekka Enberg
2006-01-20 14:47                 ` Jan Engelhardt
2006-01-15 11:56             ` Pavel Machek
2006-01-14 16:04   ` Ed Tomlinson
2006-01-14 17:23     ` Lee Revell

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=1137349821.25801.30.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@earthworm.de \
    --cc=marc@perkel.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