public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Tassonis <timtas@cubic.ch>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Michael Krufky <mkrufky@linuxtv.org>,
	Adrian Bunk <bunk@kernel.org>, Pavel Machek <pavel@suse.cz>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: reiser4 for 2.6.27-rc1
Date: Wed, 13 Aug 2008 16:00:10 +0200	[thread overview]
Message-ID: <48A2E8EA.2060704@cubic.ch> (raw)
In-Reply-To: <20080813143613.61101a5e@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>> And yes, I think Hans lost his right to decide over the name because of 
>> what he has done. That is no disrespect for his work, only for him as 
>> person in general, and I do strongly disrespect him as a person.
> 
> So should ever reissue of a work by Gary Glitter have the name removed
> from the cover, every opera by Wagner have the name removed for his
> attitudes ?
> 
> History is a one way street, and you might as well have the fs known the
> way it is so that people remember "reiser oh wasn't he the guy who.." -
> unless you are trying to market the fs I guess.
> 
> Alan

Well I think I said, I wouldn't be in favour of renaming reiser3, also 
for above reasons (although I didn't mention them).

I am in favour of renaming reiser4 exactly because it is not yet in and 
naming a filesystem after its author is not as automatic as putting the 
name of the singer on a record sleeve.

And I do give a dog's turd about what Hans might think about this.

It won't be my decision, anyway....

Tim





  reply	other threads:[~2008-08-13 14:01 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 12:26 reiser4 for 2.6.27-rc1 Tim Tassonis
2008-08-13 12:58 ` Pavel Machek
2008-08-13 13:18   ` Adrian Bunk
2008-08-13 13:24     ` Michael Krufky
2008-08-13 13:34       ` Adrian Bunk
2008-08-13 13:30         ` Alan Cox
2008-08-13 13:46         ` Michael Krufky
2008-08-13 14:50           ` Frans Meulenbroeks
2008-08-13 23:04         ` Jeremy Fitzhardinge
2008-08-25 20:09           ` Bill Davidsen
2008-08-13 13:37       ` Tim Tassonis
2008-08-13 13:36         ` Alan Cox
2008-08-13 14:00           ` Tim Tassonis [this message]
2008-08-13 14:59             ` Ryan Hope
2008-08-13 15:24               ` Tim Tassonis
2008-08-13 16:18                 ` Jeff Chua
2008-08-13 16:30                 ` Ryan Hope
2008-08-25 20:04           ` Bill Davidsen
2008-08-13 13:56     ` Andi Kleen
2008-08-13 14:02       ` Tim Tassonis
  -- strict thread matches above, loose matches on Subject: below --
2008-08-01 13:49 Ryan Hope
2008-08-01 16:25 ` Theodore Tso
2008-08-01 16:34   ` Ryan Hope
2008-08-01 16:45     ` Theodore Tso
2008-08-01 18:15       ` Ric Wheeler
2008-08-01 22:40         ` Edward Shishkin
2008-08-02 15:47           ` Ryan Hope
2008-08-02 22:56             ` Edward Shishkin
2008-08-02 23:18               ` Ryan Hope
2008-08-04 11:11                 ` Edward Shishkin
2008-08-04 11:18                   ` Dushan Tcholich
2008-08-04 11:34                     ` Dushan Tcholich
2008-08-02  2:30   ` Alexey Dobriyan

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=48A2E8EA.2060704@cubic.ch \
    --to=timtas@cubic.ch \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkrufky@linuxtv.org \
    --cc=pavel@suse.cz \
    /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