[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Why we have NULL txn_id for delta representation?

From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: 2006-03-10 14:52:13 CET

Thanks Karl.
Yes, understood about the 'bubble-up' stuff from the
subversion/libsvn_fs_base/notes/structure doc.
Will see which gets cloned whether nodes table entries or their
representations too which I don't think

With regards
Kamesh Jayachandran

kfogel@collab.net wrote:
> Kamesh Jayachandran <kamesh@collab.net> writes:
>
>> My current understanding of mutablity is that history(past) should not
>> be muted, not the internal representation of it, i.e representation
>> could change from 'fulltext' to 'delta' and viceversa as long as view
>> of the consumers of the representation is same before and after this
>> change.
>>
>
> This is correct, yes.
>
>
>> I am yet to see how/where the cloning happens.
>> I guessed by reading the subversion/libsvn_fs_base/fs-history doc that
>> on each change of the path all the path components are cloned and
>> corresponding changes are done to a clone, wondered that there should
>> be no such cloning in 'representations' and 'strings' tables as the
>> youngest is always fulltext.
>>
>
> Cloning happens during the process of committing a change to a path.
> Before I explain it, let me ask: do you know what the "bubble up"
> algorithm in the Subversion repository is? That is a prerequisite for
> understanding how trees and history are stored in the repository.
>
> Best,
> -Karl
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 10 14:54:13 2006

This is an archived mail posted to the Subversion Dev mailing list.