> 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?
>

I do not believe that this is the case. During the merge, any new files on
the branch are basically copies from the branch. They are added (with
history), and simply point back to the version added in the branch.

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.
>
>
Cheers,
Daniel B.