public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Stroetmann <stroetmann@ontolab.com>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	Tux3 <tux3@tux3.org>, Andreas Karlsson <andreas@proxel.se>,
	Daniel Phillips <daniel.raymond.phillips@gmail.com>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: Tux3 Report: Meet Shardmap, the designated successor of HTree
Date: Tue, 25 Jun 2013 02:34:11 +0200	[thread overview]
Message-ID: <51C8E583.3000701@ontolab.com> (raw)
In-Reply-To: <CAFLxGvxF-YyYWM3Yr8+62r5sE2iFOptTQftPjf5i=azRAqtVKg@mail.gmail.com>

Dear Mr. Richard Weinberger:

Thank you very much for the reminder and the prove again that a profound 
discussion seems not to be possible. Even more important is the point 
that the discussion related with the ReiserFS was different than this 
discussion, because this time I have not presented the LogHashFS to the 
open source community, but another person has taken copyright 
descriptions from my websites and wanted to make it an open source 
project and this even by the support of another company, which by the 
way has its very own business strategy.

Now, other and I have heard what we wanted: In the moment you have no 
more arguments you become offensive and begin to mob and to intirigue. 
Besides this, ReiserFS is virtually dead .... Furthermore, that 
journalist from the Linux Magazin said it due to other political and 
economical reasons in the B.R.D. as well and most potentially did never 
something that is important for the open source community. Sooner or 
later he will get a letter from my attorney  for this offensive with the 
demand to beg for pardon publicly in the ReiserFS and Tux3 mailing lists.

Said this, I will not sent any e-mails to this Chuck Nonsense thread 
anymore. It was a mistake at all to try it again.



Sincerely
Christian Stroetmann

> Let's do the same as in 2009[1] and finish this thread.
>
> [1] http://www.spinics.net/lists/reiserfs-devel/msg01543.html
>
> --
> Thanks,
> //richard
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2013-06-25  0:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 17:02 Tux3 Report: Meet Shardmap, the designated successor of HTree Daniel Phillips
2013-06-20 19:11 ` Christian Stroetmann
2013-06-20 20:27   ` Daniel Phillips
2015-04-15 18:00     ` Christian Stroetmann
2013-06-24 14:18   ` Pavel Machek
2013-06-24 15:16     ` Christian Stroetmann
2013-06-24 15:39       ` Andreas Karlsson
2013-06-24 17:19         ` Christian Stroetmann
2013-06-24 18:20           ` richard -rw- weinberger
2013-06-25  0:34             ` Christian Stroetmann [this message]
2013-06-25  0:15               ` David Lang
  -- strict thread matches above, loose matches on Subject: below --
2013-06-19  2:31 Daniel Phillips
2013-06-19 18:17 ` Christian Stroetmann

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=51C8E583.3000701@ontolab.com \
    --to=stroetmann@ontolab.com \
    --cc=andreas@proxel.se \
    --cc=daniel.raymond.phillips@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=richard.weinberger@gmail.com \
    --cc=tux3@tux3.org \
    /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