public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Perkel <marc@perkel.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Lee Revell <rlrevell@joe-job.com>,
	"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 07:11:40 -0800	[thread overview]
Message-ID: <43CA662C.1040204@perkel.com> (raw)
In-Reply-To: <1137315139.3001.5.camel@laptopd505.fenrus.org>



Arjan van de Ven wrote:
>>> OK, suit yourself.
>>>
>>> Anyway, there was no need to get so defensive - Arjan was just telling
>>> you that it's not up to the kernel developers when reiser4 gets in, it's
>>> up the the reiser4 developers when they submit it in a mergeable state
>>> (they know what that is), so you should ask the reiser4 people when they
>>> plan to do that.
>>>
>>> Lee
>>>
>>>   
>>>       
>> 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.
>>     
>
> please stop trolling.
>
> I gave you a polite answer that the exact same question was asked
> recently, and answered. If you are then too lazy to go look in the
> archive even then..... ok here is it:
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0601.0/1840.html
>
> I even pointed out a mailinglist that's best suited for detailed
> follow-on questions. 
>
> Your "political" and other crap you're spewing here shows that you're
> not actually interested in the answer, but just want to start a
> flamewar. THAT is not reasonable on linux-kernel. If you want to start a
> flamewar at least do it for a technical topic/reason.
>
>   
I just asked a simple question about what the status of a merge was. No 
one has responded to my question yet. All I'm hearing is that Reiser 4 
is a prohibited subject.

  reply	other threads:[~2006-01-15 15:11 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 [this message]
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
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=43CA662C.1040204@perkel.com \
    --to=marc@perkel.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@earthworm.de \
    --cc=rlrevell@joe-job.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