From: "John D. Heintz" <jheintz@pobox.com>
To: Hans Reiser <reiser@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Do xml-like namespaces make sense for Reiser4? (re: metas thread)
Date: Tue, 13 Apr 2004 13:23:00 -0500 [thread overview]
Message-ID: <407C3004.3070401@pobox.com> (raw)
In-Reply-To: <407C279A.3060303@namesys.com>
Hans Reiser wrote:
> John D. Heintz wrote:
>
>> Hans Reiser wrote:
>>
>> Let me verify something: You are suggesting that the "metas"
>> namespace be the entry point for all of the plugin namespaces? I had
>> assumed that each plugin would create it's own. That does certainly
>> reduce the scope of my problem.
>
>
> It can use metas, but what it does is up to it. metas is a style
> convention.
>
Okay, that is what I thought originally. That still means that user
defined names and plugin defined names can in general conflict though.
>
> this is the beauty of there being an official maintainer for reiserfs
> to handle such issues;-)
>
I would have been much happier to hear some strategy would enable
plugins names to disambiguate themselves from each other and user
defined names. In practice you might be right that a few dozen plugins
can be "officially" integrated without too much trouble. Also, this
issue could be dealt with later as well - I don't think now is the only
opportunity for addressing it.
> plugins are not created as easily as files;-), there will be few
> enough that I can manage the issue as it happens
>
Yes, in the short to medium term you are probably right that you can
deal with these issues as they happen. I'd like there to be some better
way of dealing with resolving conflicts from unified namespaces then
always "ask Hans".
Does some sort of syntactic shorthand actually break the set theoretic
naming system rules? Or is this just something you view as needless
complexity?
Thanks for the replies,
John Heintz
next prev parent reply other threads:[~2004-04-13 18:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 15:45 Do xml-like namespaces make sense for Reiser4? (re: metas thread) John D. Heintz
2004-04-12 16:00 ` Hubert Chan
2004-04-12 19:21 ` John D. Heintz
2004-04-12 21:28 ` Hubert Chan
2004-04-12 18:15 ` Hans Reiser
2004-04-12 18:59 ` Hubert Chan
2004-04-12 19:12 ` John D. Heintz
2004-04-13 14:40 ` John D. Heintz
2004-04-13 16:31 ` Hans Reiser
2004-04-13 16:57 ` John D. Heintz
2004-04-13 17:06 ` Grant Miner
2004-04-13 18:09 ` John D. Heintz
2004-04-13 18:36 ` Grant Miner
2004-04-13 17:47 ` Hans Reiser
2004-04-13 18:23 ` John D. Heintz [this message]
2004-04-13 18:28 ` Hans Reiser
2004-04-13 18:47 ` John D. Heintz
2004-04-13 20:31 ` Valdis.Kletnieks
2004-04-14 2:18 ` Enrique Perez-Terron
2004-04-14 15:06 ` John D. Heintz
2004-04-14 23:39 ` Enrique Perez-Terron
2004-04-14 2:50 ` David Masover
2004-04-14 15:12 ` John D. Heintz
2004-04-15 0:28 ` David Masover
2004-04-15 15:15 ` John D. Heintz
2004-04-16 1:04 ` David Masover
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=407C3004.3070401@pobox.com \
--to=jheintz@pobox.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.