Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
versioncontrol:vendorbranches [2006/10/07 14:18] – better wikilinks in "monotone implementation" chapter LapoLuchiniversioncontrol:vendorbranches [2022/10/07 01:54] (current) – Move bakeoff stuff under a single namespace KubilayKocak
Line 5: Line 5:
  
 ===== SVN Implementation ===== ===== SVN Implementation =====
 +
 +Subversion does not need to provide particular support for vendor branches, they are treated as just another tree of files.  You can develop procedures to make it easier to manage third party code.  I have one set at
 +http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/ImportingIntoSubversion.  The Subversion book also has a [[http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html|chapter dealing with vendor branches]].
  
 ===== Hg Implementation ===== ===== Hg Implementation =====
Line 60: Line 63:
 ===== Monotone Implementation ===== ===== Monotone Implementation =====
 **Supported** **Supported**
-(also see [http://venge.net/monotone/wiki/FeatureVendorBranches monotone:[[/FeatureVendorBranches|FeatureVendorBranches]]])+(also see [[http://venge.net/monotone/wiki/FeatureVendorBranches|monotone:FeatureVendorBranches]])
  
-Any branch can be used as a Vendor Branch.  Unlike CVS, vendor branches are not treated specially in ["Monotone"].+Any branch can be used as a Vendor Branch.  Unlike CVS, vendor branches are not treated specially in [[/Monotone|Monotone]].
  
 There are two aspects to this requirement that are often used together: There are two aspects to this requirement that are often used together:
  • versioncontrol/vendorbranches.1160230721.txt.gz
  • Last modified: 2006/10/07 14:18
  • by LapoLuchini