branch=>merge: additions + modifications twice in repository?

Hi all out there,

and I suppose this behaviour has not changed over the last few
years and probably is not meant to change at all:

Any addition or modification done and committed on a branch is
physically added a second time to the repository once the branch
is merged into trunk and committed, right?

If development makes working on an isolated branch necessary
that has priority of course. Yet if e.g. 200MB binaries (jpeg) are to
be added on a branch and then would have to be added once again
on trunk, thus doubling the space used in the repository, one
begins to think. Particularly so in the case branching is not
necessary for specific development reason, but merely to use
some spare time as those resources are not to show up on
production before several months.

Supposedly just using an extra working copy of trunk and putting it
away until time comes is the better solution to this, foregoing
concurrent spare time work of course. Or finding other spare time
jobs.

TIA for confirmation a/o other suggestions.

JH
---------------------------------------
Freedom quote:

     Was ist denn Freiheit?
     Die Möglichkeit so zu leben, wie du willst.
               -- Marcus Tullius Cicero

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2403185

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-03 12:29:27 CEST