Clarify one point: The file@base (or the file @head) refers to the file I am currently updating, right?
I am very curious why the server needs to re-compute the skip-delta. Is there any rule to guide the server which pristine version to be delta-ed against? To optimize the delta (specifically, to optimize the storage for the delta)? Thanks. Bo On Wed, Mar 6, 2013 at 7:05 AM, Daniel Shahaf <d...@daniel.shahaf.name>wrote: > Branko Čibej wrote on Wed, Mar 06, 2013 at 06:41:40 +0100: > > On 06.03.2013 06:21, Daniel Shahaf wrote: > > > Bo Chen wrote on Tue, Mar 05, 2013 at 23:49:06 -0500: > > >> Can anyone help me make clear the following questions? Thanks very > much. > > >> > > >> I make some updates, and the SVN client generates the delta and sends > it to > > >> the SVN server. Does the server simply store this delta to the > repository, > > >> or do something more? > > >> > > > The latter. The client always generates a delta against file.c@HEAD, > > > but the filesystem stores skip-deltas. > > > > That would be file@BASE, since that's what the client has a pristine > > version of. :) > > It @BASE and @HEAD will be the same node-rev, else the commit will fail. >
