Hello,
When using a branch for developing a particular feature
for some longer time, then typically there are much
more changes merged from trunk to the branch from day
to day than the work itself done on the branch.
Now when doing a merge from trunk to the branch,
every merged file gets a new node in the svn repository,
even if the file will be the same as in trunk, correct?
This means, when switching between trunk and the branch,
the svn server work needed for the switch is proportional
to the (large) number of changes done on trunk
since the branch creation, not proportional to the
(small) number of differences between trunk and branch.
Is this correct?
(If yes, maybe some node hash value map can be used
to identify nodes in the branch which are equal
to the corresponding node in trunk, avoiding
the branch "degeneration"?
This also would reduce the repository size
a lot, because most merge changes in the branch
don't have to be stored separately.)
A side effect I noticed is that when switching,
also files which have been changed since branch creation
but which are equal on the trunk and branch (due to merging)
get a new file time. This can cause ugly recompiles.
Cheers,
Folker
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 8 18:41:50 2004