From: Hans Reiser <reiser@namesys.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@digeo.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>,
reiserfs-list@namesys.com
Subject: Re: silent semantic changes in reiser4 (brief attempt to document the idea of what reiser4 wants to do with metafiles and why
Date: Tue, 07 Sep 2004 13:16:15 -0700 [thread overview]
Message-ID: <413E170F.9000204@namesys.com> (raw)
In-Reply-To: <20040831131201.GA1609@elf.ucw.cz>
Pavel Machek wrote:
>Hi!
>
>
>
>>Answer: choose obscure names
>>
>>Problem (all credit to Mr. Demidov for identifying this problem, I
>>argued the other viewpoint, and I can only claim the wisdom to know
>>that I lost the argument): names like "..metas" are ugly to new users,
>>who don't really care for languages that use punctuation in their
>>keywords.
>>
>>Answer
>>
>>don't make them too obscure, experienced namespace developers know
>>that the problem of polluting the namespace is not really as big a
>>deal as beginners think it is, and Clearcase and the WAFL filesystem
>>manage to get by just fine, whereas the problem of putting punctuation
>>marks into names and syntax is a big deal for newbies to the system.
>>Name it "metas" not "..metas", and users will never experience it as a
>>real problem, and newbies will never be annoyed by a-rhythmic
>>punctuation. Note: if Linus disagrees, it is not the most important
>>thing in this design, "..metas" isn't the end of the world.
>>
>>
>
>What about choosing just "..." instead of "metas"? "metas" is string
>that needs translation etc, while "..." is nicely neutral.
>
>cat /sound_of_silence.mp3/.../author
>
>does not look bad, either...
> Pavel
>
>
"..." is pretty good, but I think it has been used by others, but I
really forget who. I could live with "...", but I think "metas" and
"..metas" will collide less often. Apparently Meta is a finnish name or
something, so Linus does not like it. The exact string is really not
very important to me. I agree that "..." is elegant.
Hans
next prev parent reply other threads:[~2004-09-07 20:27 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 20:21 silent semantic changes in reiser4 (brief attempt to document the idea of what reiser4 wants to do with metafiles and why Hans Reiser
2004-08-31 13:12 ` Pavel Machek
2004-08-31 13:36 ` Christian Mayrhuber
2004-09-07 20:16 ` Hans Reiser [this message]
2004-09-07 20:59 ` Pavel Machek
2004-09-08 9:14 ` Romano Giannetti
2004-09-07 21:05 ` William Stearns
2004-09-07 22:09 ` Robin Rosenberg
2004-09-09 9:03 ` silent semantic changes in reiser4 (brief attempt to document the idea ofwhat " Theodore Ts'o
2004-09-09 17:23 ` William Lee Irwin III
2004-09-09 18:09 ` Gunnar Ritter
2004-09-09 19:15 ` Hans Reiser
2004-09-09 20:45 ` Paul Jakma
2004-09-10 0:57 ` Hans Reiser
2004-09-10 1:15 ` Paul Jakma
2004-09-10 5:04 ` Hans Reiser
2004-09-10 5:53 ` viro
2004-09-10 6:52 ` Hans Reiser
2004-09-10 7:05 ` viro
2004-09-10 7:30 ` Hans Reiser
2004-09-10 16:49 ` Lee Revell
2004-09-10 17:23 ` viro
2004-09-10 7:21 ` Hans Reiser
2004-09-10 7:33 ` viro
2004-09-10 7:46 ` Hans Reiser
2004-09-10 8:18 ` viro
2004-09-10 9:20 ` Alan Cox
2004-09-10 17:48 ` Hans Reiser
2004-09-10 17:07 ` Alan Cox
2004-09-10 13:08 ` Horst von Brand
2004-09-10 3:22 ` Horst von Brand
2004-09-12 20:43 ` Davide Inglima
2004-09-10 9:42 ` Helge Hafting
2004-09-10 17:42 ` Horst von Brand
[not found] ` <20040910201738.GB8698@eskimo.com>
2004-09-14 8:39 ` Helge Hafting
2004-08-31 14:09 ` silent semantic changes in reiser4 (brief attempt to document the idea of what " Mike Waychison
2004-08-31 17:55 ` V13
2004-08-31 18:17 ` Spam
2004-08-31 19:08 ` Tonnerre
2004-08-31 19:38 ` Spam
2004-09-01 3:11 ` Robin Rosenberg
2004-08-31 19:35 ` V13
[not found] ` <874qmjm51g.fsf@uhoreg.ca>
2004-08-31 20:31 ` Spam
[not found] ` <87vfezkm06.fsf@uhoreg.ca>
2004-08-31 22:15 ` Spam
2004-08-31 19:49 ` Chris Dawes
2004-09-01 6:03 ` Hans Reiser
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=413E170F.9000204@namesys.com \
--to=reiser@namesys.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=reiserfs-list@namesys.com \
--cc=torvalds@osdl.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