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

RE: Vendor braches [Was: Re: applying a merge on a non workingcopy]

From: Dale Worley <dworley_at_pingtel.com>
Date: 2005-01-24 22:31:04 CET

The crux of the "vendor branch" system is that there are two main threads of development. One is your current code. It evolves in the normal manner. The "vendor branch" evolves, but successive revisions are successive releases of the code by the vendor. When the vendor produces a new version, you check it in as a revision of the vendor branch, then merge that delta of the vendor branch into the branch that contains your code.

The remainder of the vendor branch structure is just setting up tags to record the names of the vendor's releases and to record the merges.


-----Original Message-----
From: Ulrich Eckhardt [mailto:eckhardt@satorlaser.com]

Is there a precise definition of vendor-branch structure? I know the part in
the book that speaks about 'vendor branches', but:

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 24 22:33:56 2005

This is an archived mail posted to the Subversion Users mailing list.