public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kurt Wall <kwall@kurtwerks.com>
To: linux-kernel@vger.kernel.org
Cc: Marc Perkel <marc@perkel.com>
Subject: Re: So - What's going on with Reiser 4?
Date: Sun, 15 Jan 2006 22:24:09 -0500	[thread overview]
Message-ID: <20060116032409.GJ5773@kurtwerks.com> (raw)
In-Reply-To: <43CA662C.1040204@perkel.com>

[CCs trimmed]

On Sun, Jan 15, 2006 at 07:11:40AM -0800, Marc Perkel took 0 lines to write:
> 
> 
> Arjan van de Ven wrote:
> >
> >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. 
> >
> >  
> 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.

Balderdash. You're just not "hearing" what you want to hear.

You were pointed to an answer. If all you're hearing is that Resier 4
is a prohibited subject then you're evidently incapable of following a
link or perhaps of reading. On the off chance that it is the former,
I'll quote the relevant text from the message to which Arjan pointed
you:

	"I think r4 folks are still working on Christoph's suggestions
	that include changes required for the code to be merged."

Perhaps it is that you only want to "hear" a specific answer. You've 
already written that you won't search the archives before you ask a 
question.

> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
"Last week a cop stopped me in my car.  He asked me if I had a police
record.  I said, no, but I have the new DEVO album.  Cops have no sense
of humor."

  parent reply	other threads:[~2006-01-16  3:24 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 [this message]
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=20060116032409.GJ5773@kurtwerks.com \
    --to=kwall@kurtwerks.com \
    --cc=linux-kernel@vger.kernel.org \
    --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