All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John D. Heintz" <jheintz@pobox.com>
To: Hubert Chan <hubert@uhoreg.ca>
Cc: reiserfs-list@namesys.com
Subject: Re: Do xml-like namespaces make sense for Reiser4? (re: metas thread)
Date: Mon, 12 Apr 2004 14:21:56 -0500	[thread overview]
Message-ID: <407AEC54.3060403@pobox.com> (raw)
In-Reply-To: <874qrpkwyi.fsf@uhoreg.ca>

Hi Hubert,

Hubert,

I agree with you, but I don't think our suggestions are exclusive.

An "ls" can return the contents of the directory as you suggested and a 
"cat" could return tab and newline separated content. I'm using the 
ReiserFS /etc/passwd example as a template.

What you suggested would be a good first step, I was just trying to 
intuitively make my point.

Thanks,
John


Hubert Chan wrote:

>XML namespaces seems like overkill to me, but I'll let someone more
>qualified say something more intelligent.  I just have one other
>comment.
>
>  
>
>>>>>>"John" == John D Heintz <jheintz@pobox.com> writes:
>>>>>>            
>>>>>>
>
>[...]
>
>John> Other namespaces could be added to files/directories and I'd
>John> assume something like: `cat foo.txt/reiser4:namespaces` would list
>John> all the namespaces available for a particular file.  Something
>John> like:
>John> reiser4 http://www.namesys.com/v4
>John> streams http://www.evil-empire.com/streams
>John> snapcm http://www.snapcm.com/snapcm
>
>It's probably better to do:
>
># ls foo.txt/reiser4:namespaces
>reiser4
>streams
>snapcm
># cat foo.txt/reiser4:namespaces/reiser4
>http://www.namespaces.com/v4
>
>  
>


  reply	other threads:[~2004-04-12 19:21 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 [this message]
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
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=407AEC54.3060403@pobox.com \
    --to=jheintz@pobox.com \
    --cc=hubert@uhoreg.ca \
    --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.