[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Live branching

From: Chris Rodgers <christopher.rodgers_at_cardiov.ox.ac.uk>
Date: Wed, 13 Aug 2008 21:25:21 +0100

Ryan Schmidt wrote:
> On Aug 13, 2008, at 15:13, Chris Rodgers wrote:
>> Ryan Schmidt wrote:
>>> On Aug 13, 2008, at 10:24, Chris Rodgers wrote:
>>>> Is it possible to make a branch where all but a few files continue
>>>> to follow the trunk?
>>> Not automatically, no.
>>>> This would be very similar to using "svn switch" in a working copy,
>>>> but would allow one to check out the particular combination of trunk
>>>> files and modified ones onto several machines.
>>>> I was thinking of using this for configuration files in the midst of
>>>> a bulk of code that remains the same on each machine.
>>> You can make a branch, then periodically merge desired changes from
>>> trunk to the branch using svn merge.
>> If I scripted this, what would happen to the disk usage? e.g. imagine
>> I have 20 of these "live branches" following trunk. Will I use up 20x
>> the disk space for every change committed to the repository?
> Maybe not 20x. A merge which results in a file being added should take
> virtually no additional space as Subversion should record this as a
> cheap copy. However a merge which results in a file being modified will
> record the changes of the modification anew. See this message from this
> past weekend:
> http://svn.haxx.se/users/archive-2008-08/0379.shtml

Thanks for clarifying. I'm glad to see that other people are also
interested in this sort of thing.

Is there anything else I should do to suggest this as a bug / feature to
be implemented?

Best wishes,


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-13 22:36:13 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.