From: david@lang.hm Date: Tue, 02 Oct 2007 20:54:59 GMT Subject: Re: metastore Message-ID: In-Reply-To: <20071002203941.GA18008@lapse.madduck.net> On Tue, 2 Oct 2007, martin f krafft wrote: > also sprach 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? you merge two uptream branches that disagree about the attributes >> 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? it's very possible that I am misunderstanding, but do we really want to have to go back to the parent to duplicate things when creating a new commit? and aren't you supposed to be able to have more then one parent? if you do, which one would you use? David Lang