public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Valdis.Kletnieks@vt.edu
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	linux-kernel@vger.kernel.org,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Matthias Andree <matthias.andree@gmx.de>,
	Grzegorz Kulewski <kangur@polcom.net>,
	Diego Calleja <diegocg@gmail.com>,
	arjan@infradead.org, caleb@calebgray.com
Subject: Re: Reiser4 Inclusion
Date: Thu, 20 Jul 2006 00:36:30 +0200	[thread overview]
Message-ID: <44BEB3EE.5020501@imap.cc> (raw)
In-Reply-To: <200607192009.k6JK9des004285@turing-police.cc.vt.edu>

[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]

On 19.07.2006 22:09, Valdis.Kletnieks@vt.edu wrote:

> On Wed, 19 Jul 2006 21:12:21 +0200, Tilman Schmidt said:
> 
>>On 19.07.2006 21:04, Valdis.Kletnieks@vt.edu wrote:
>>
>>>Which part of "read Documentation/SubmittingPatches.txt and do what it says,
>>>or it doesn't get into the kernel" do you have trouble understanding?
>>
>>None. Why do you think I'd have? And what relevance does this have to
>>the present discussion?
> 
> So in other words, you're trying to tell us about what code should or
> shouldn't allow into the kernel when you don't have even a clue what's
> required on a purely technical level, or how the code gets into the kernel.

That's entirely uncalled for. If you deem it necessary to resort to
insults when you are out of arguments then please go looking for another
victim. I consider the discussion closed.

-- 
Tilman Schmidt                          E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]

  reply	other threads:[~2006-07-19 22:36 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17  3:02 Reiser4 Inclusion Caleb Gray
2006-07-17  9:25 ` Arjan van de Ven
2006-07-17 11:48   ` Grzegorz Kulewski
2006-07-17 11:57     ` Alexander Gran
2006-07-17 14:06     ` Diego Calleja
2006-07-17 14:31       ` Grzegorz Kulewski
2006-07-17 15:51         ` Matthias Andree
2006-07-18  7:59           ` Jan Engelhardt
2006-07-18 20:47             ` Matthias Andree
2006-07-19  1:19               ` Joshua Hudson
2006-07-19  9:27               ` Tilman Schmidt
2006-07-19 11:00                 ` Krzysztof Halasa
2006-07-19 11:03                 ` Pekka Enberg
2006-07-19 15:32                   ` Tilman Schmidt
2006-07-19 19:04                     ` Valdis.Kletnieks
2006-07-19 19:12                       ` Tilman Schmidt
2006-07-19 20:09                         ` Valdis.Kletnieks
2006-07-19 22:36                           ` Tilman Schmidt [this message]
2006-07-19 20:29                       ` Jeff V. Merkey
2006-07-19 22:01                         ` Matthias Andree
2006-07-19 22:34                     ` Helge Hafting
2006-07-17 15:52         ` gmu 2k6
2006-07-17 15:57           ` Alexander Gran
2006-07-17 19:01         ` Horst von Brand
2006-07-17 15:13     ` Jeff Anderson-Lee
2006-07-17 15:56       ` Matthias Andree
2006-07-17 20:48       ` Erik Mouw
2006-07-18  0:49         ` Jeff Dike
2006-07-18 11:43           ` Christoph Hellwig
2006-07-17  9:44 ` Patrick McFarland
2006-07-17 11:07 ` Diego Calleja
2006-07-17 14:38 ` Alex Riesen
2006-07-17 18:05 ` Valdis.Kletnieks
2006-07-18 23:10   ` Nix
2006-07-19  6:56 ` Reiser4 ACLs Marc Perkel
2006-07-19 15:03   ` Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
2006-07-17 22:34 Reiser4 Inclusion linux
     [not found] <06Jul25.011533edt.35900@gpu.utcc.utoronto.ca>
2006-07-30 22:02 ` Tilman Schmidt

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=44BEB3EE.5020501@imap.cc \
    --to=tilman@imap.cc \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=arjan@infradead.org \
    --cc=caleb@calebgray.com \
    --cc=diegocg@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=kangur@polcom.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@gmx.de \
    --cc=penberg@cs.helsinki.fi \
    /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