All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: "John D. Heintz" <jheintz@pobox.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Do xml-like namespaces make sense for Reiser4? (re: metas thread)
Date: Thu, 15 Apr 2004 20:04:07 -0500	[thread overview]
Message-ID: <407F3107.5030401@slaphack.com> (raw)
In-Reply-To: <407EA70F.6010301@pobox.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John D. Heintz wrote:
| [...]
| Is this behavior currently part of Reiser4? I don't remember seeing it
| anywhere, but I do remember reading something about inheritence being
| needed for various features. Is this the same as inheritence?

I don't know enough about how Reiser4 currently works.  I last tried it
a few months ago, although I might try it again soon.  But in a few
months, it becomes such a moving target that I think I'll have to read
the whitepaper again.  Just haven't gotten the time.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQH8xBngHNmZLgCUhAQKqfg//dpUOU53eoCQzseF1F2okf1BZRE42Ij37
n/e1T1HKg5llAo+IG8W8FZ25eEDzqM17Nt/ZuhdvjqMLYUp3kMBBLrZOpFhxmNNG
boTnjDakjEu2BCm3xNYEGoURBqs0MNUz85h9inrYML694nL90OkzrVP0xQBhYKI6
EmmTXVsqk+IZZ52OworcqlqV60GjZUI7F3j6vTFyjQCWat8mEc8fbRqFgI2/NlDO
U0W6GClZA3NAEInYdUS1iVjILlUKC68GhiCs8gdGMKDBYoiJuHus/kvwzNb7wMvC
lkA/GvTDxT1ikzarL3XfCqRzzeKYcgSJw6a4N7tOptBt0p6bZa+YK5bE0/EXD5Yb
/LVIQA6xG6MJxQZUgrt6UiNvbJEvr/N78oBrSdMfIY0mSIn+FZZmJqrTT67SjkF2
Rv5c5dxB9mItEJmC576cIQZ7FY+XSh3kjgkvQRYplwZeyFLeZU4thsiLBtn1ARi2
1jt0sNZzKiIYpqmTKDYXQJ0lfd/jRRWNNgQy0aGt4RaKT2T181TPKjlz92n2BbNQ
+nf1nmMQ9rnw9VQ3HhiUrBAQS0ufAY33ztpD/2/OoNfwvOEAOnzjZJCY9+Nhlbxg
mOQXr3aGrP1xm7wCYgTy7A1Q2z5U9AxV31/f8ELLwFxDlQrBIHYCr67W7WSIb4dH
+a2HCw1q3Ls=
=4vk3
-----END PGP SIGNATURE-----

      reply	other threads:[~2004-04-16  1:04 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
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 [this message]

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=407F3107.5030401@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=jheintz@pobox.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.