Re: metastore

From: martin f krafft <madduck@madduck.net>
Date: Oct 2, 2007, 20:39 UTC
Message-ID: <20071002203941.GA18008@lapse.madduck.net>
In-Reply-To: <Pine.LNX.4.64.0710021327371.24697@asgard.lang.hm>

also sprach david@lang.hm <david@lang.hm> [2007.10.02.2129 +0100]:

> 1. you do want to be able to manipulate them
>
> 1a. how do you reconcile a conflict during a merge?

How could there be a conflict if you can't make local changes because you can't represent the attributes locally/natively?

> 2. git is a series of snapshots, what does it mean to 'stay unchanged'?

In simple terms, let (content,A,B) be an object with content "content" and extended attributes A,B, and B cannot be represented locally, but a new object is committed with a change to attribute A (content2,A2), then the result is (content2,A2,B), as B simply comes from the (corresponding object of the) parent.

Or am I totally misunderstanding?

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
when compared to windoze, unix is an operating system.
 
spamtraps: madduck.bogus@madduck.net