All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: "Alexander G. M. Smith" <agmsmith@rogers.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Recursive modified-timestamp?
Date: Sun, 02 Jan 2005 09:52:33 -0800	[thread overview]
Message-ID: <41D834E1.6030404@namesys.com> (raw)
In-Reply-To: <4329085595-BeMail@cr593174-a>

Alexander G. M. Smith wrote:

>
>Possibly.  But I'd like to generalize it a bit.  Percolated attributes are
>perhaps a better more general idea.  We already have inherited attributes
>(such as security of children being inherited from the parent) so going in
>the other direction isn't all that big step, it just needs an application,
>like your modification detection system.
>  
>
The general form of inheritance should not be restricted to inheriting 
from parents.  Parents should merely be a default if nothing is 
specified as what one inherits from.  And when one inherits, one can 
write through to what one inherits from, at least by default.

At least, such are my thoughts on the matter.

Hans

  reply	other threads:[~2005-01-02 17:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-01 18:59 Recursive modified-timestamp? Alexander G. M. Smith
2005-01-02 17:52 ` Hans Reiser [this message]
2005-01-06 22:31   ` David Masover
  -- strict thread matches above, loose matches on Subject: below --
2004-12-31  9:47 Recursive modfied-timestamp? Fred Schaettgen
2004-12-31 22:49 ` David Masover
2005-01-01  0:43   ` Recursive modified-timestamp? Fred Schaettgen
2005-01-01  3:12     ` Alexander G. M. Smith
2005-01-01 11:56       ` Fred Schaettgen
2005-01-01 12:28       ` Piotr Neuman
2005-01-01 13:20         ` Fred Schaettgen
2005-01-01 17:08           ` Piotr Neuman
2005-01-01 18:18             ` Fred Schaettgen

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=41D834E1.6030404@namesys.com \
    --to=reiser@namesys.com \
    --cc=agmsmith@rogers.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.