Re: The cost of fulltexts on branches

One thing that might substantially help in this respect is an improvement
that could be made to merges from trunk to branch without changing the BDB
structure.

Suppose trunk has a file A that is copied into a branch. The branch will
have just a small pointer to A.

Suppose A is then modified to create A', but A has not been modified in the
branch. When the trunk changes are merged to the branch and then checked in,
this is unfortunately treated as a creation of a new A'' in the branch,
which is stored full text in the repository. Ideally, it would notice that A
was not modified in the branch work area, and it would optimize the checkin
after the merge to just create a pointer back to A'. That could
substantially decrease the space necessary to hold branch information.

That sort of optimization is done (I'm pretty sure) when the trunk gets a
new file that is brought over to a branch, but not when there are changes to
an existing file.

Patrick Rusk

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 30 17:50:29 2004