All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John D. Heintz" <jheintz@pobox.com>
To: Enrique Perez-Terron <enrique.perez-terron@norway.online.no>
Cc: reiserfs-list@namesys.com
Subject: Re: Do xml-like namespaces make sense for Reiser4? (re: metas	thread)
Date: Wed, 14 Apr 2004 10:06:17 -0500	[thread overview]
Message-ID: <407D5369.5090509@pobox.com> (raw)
In-Reply-To: <1081909092.6753.64.camel@arabia.home.lan>

Enrique,

Enrique Perez-Terron wrote:
> On Tue, 2004-04-13 at 22:31, Valdis.Kletnieks@vt.edu wrote:
> 
>>On Tue, 13 Apr 2004 13:47:12 CDT, "John D. Heintz" said:
>>
>>>foo/nsa:permissions -> foo/nsa.gov/secure-linux/permissions
>>>
>>>This assumes a mapping from "nsa" -> "nsa.gov/security/".
> 
> 
> Implementing a mapping "nsa" -> "nsa.gov/security/" does not remove the
> headache of what to do with a tarball containing a directory named
> "nsa".


A directory or file named "nsa" doesn't conflict with this scheme, look 
more closely at the left hand side: foo/nsa:permissions

foo/nsa/permissions wouldn't receive the same treatment and would 
instead just be a regular file or directory lookup.

Two conditions are necessary to trigger the syntactic manipulation I'm 
suggesting:
1) a ':' must be present in the name being resolved (i.e. nsa:permissions)
2) The prefix before the ':' must be in the mappings (i.e. nsa)

Only if both of those are present does anything special happen.

A tarball containing "secure-linux/nsa/src/*.c" wouldn't break anything, 
and is so likely that no suggestion should risk breaking this case.

However, a tarball containing "secure-linux/nsa:src/*.c" would indeed 
break my scheme. I'm suggesting this is an ignorably small likelyhood. 
Others are free to disagree with this of course.

John Heintz


  reply	other threads:[~2004-04-14 15:06 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
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 [this message]
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=407D5369.5090509@pobox.com \
    --to=jheintz@pobox.com \
    --cc=enrique.perez-terron@norway.online.no \
    --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.