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

Re: Branch on change feature?

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Tue, 4 Aug 2009 19:13:25 -0500

On Aug 4, 2009, at 18:26, Shaun Pinney wrote:

> Does Subversion provide a 'branch-on-change' or 'deferred branch'
> feature?
> For example, if I have a directory 'A' in the repository can I
> create a
> duplicate directory 'B' which transparently tracks the contents/
> revisions in
> 'A' so that commits to 'A' are seen by updates to 'B' and, when a
> commit
> occurs to a file in 'B', the file branches and no longer tracks
> 'A'? This
> is paraphrased from a request I heard earlier today.

Not in that form, no. If you create branch B, it is a copy of A, and
separate from A. Changes made to A stay in A, changes made to B stay
in B. If you want to bring changes from A to B or vice versa, you
must explicitly use the "svn merge" command.

If you already know now that you aren't going to make changes to B
until later, you could wait until that time to create B, to save
yourself from having to do an initial merge.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-05 02:14:27 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.