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

Keeping common files in trunk and branch identical

From: Asbjørrn Sæbø <gaffe_1_at_live.com>
Date: Thu, 26 Nov 2009 15:10:58 +0100

I would like to have a branch for a different variant of our software.  In the branch, some of the files will be changed.  The other files I would like to keep identical between trunk and the branch.  That is, I would like to avoid the parallel maintenance of the same file in the trunk and the branch.  Are there any "magical" tricks I can do to keep some files more or less automatically synchronized and identical between the trunk and the branch?

Basically, what I think I need is some kind of "overlay" mechanism, where a branch would take it's files from the trunk, _unless_ they have been changed in the branch.  And where a change applied to the trunk would also take effect in the branch.  That is, the branch would, for files that have not been changed in the branch, just follow the trunk.  Is anything like this possible?

(It seems to me that Aegis may have some form of "inheritance" between branches, where a change that is needed in more than one branch may be applied to their common ancestor.  Something like that might be similar to what I need.)

With kind regards
Asbjørn Sæbø

                                               
_________________________________________________________________
Windows Live Hotmail: Your friends can get your Facebook updates, right from Hotmail®.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_4:092009

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

Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-11-26 15:13:19 CET

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.