[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: Shaun Pinney <shaun.pinney_at_bil.konicaminolta.us>
Date: Tue, 4 Aug 2009 17:43:19 -0700

Thanks Greg and Ryan. I think the branch and manually merge option will
work pretty well for us. And honestly, I'm a bit relieved there's only a
manual merge option available :). We'll be trying this out soon.


-----Original Message-----
From: Greg Troxel [mailto:gdt_at_ir.bbn.com]
Sent: Tuesday, August 04, 2009 5:04 PM
To: Shaun Pinney
Cc: users_at_subversion.tigris.org
Subject: Re: Branch on change feature?

Shaun Pinney <shaun.pinney_at_bil.konicaminolta.us> writes:

> 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
> '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.


But, if you do

svn copy foo/branches/A /foo/branches/B

and then periodically go to B and do 'svn merge foo/branches/A' you will
get sort of what you want, except that changes to files in A will still
try to be merged to B.


To unsubscribe from this discussion, e-mail:


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