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

Vendor branches: Current guidance?

From: D D L <ddl877_at_outlook.com>
Date: Thu, 22 May 2014 13:55:33 -0400

Hello all,
What are the currently accepted best practices / tools for maintaining "vendor" branches?
I've seen the page at:http://svnbook.red-bean.com/en/1.7/svn.advanced.vendorbr.html
I ask about updated guidance since:
1) I notice some (?) churn for this section in the SVN Book repository:https://code.google.com/p/svnbook/source/browse/trunk/en/book/ch04-branching-and-merging.xml
2) There appears to be both "svn_load_dirs" and "svn-merge-vendor.py" scripts at:http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/
I'm trying to refactor out some thirdparty code from my codebase, and I'd like to set things up correctly. (I'd hate to screw things up just because I accidentally read a soon-to-be-outdated HOWTO.)
Secondarily, what kind of issues can I expect to encounter as I setup and use a vendor branch style deployment?
Thank you,David

                                               
Received on 2014-05-22 19:56:10 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.