The online subversion book talks a bit about vendor branches here:
http://svnbook.red-bean.com/en/1.1/ch07s05.html
The book describes keeping a copy of each vendor release in the
repository. This is generally necessary to generate a changeset from
previous revision to new revision. However in our case all our vendor
drops already exist in another subversion repository. Since the merge
command can pull the change sets directly from these repositories it
doesn't seem necessary to keep the full source of each vendor drop in
our repository also, what is important however is to keep track of the
revision number last applied. Sorta like svn:merge-info.
So I tweaked the procedure as follows:
1) Determine which the last applied vendor revision number:
svn propget vendor-revision
Note property value: %LAST_REVISION%
2) Determine current vendor version:
svn info vendorurl
Note Revision number: %REVSION%
3) Merge changesets into working copy (from directory corresponding to
the trunk):
svn propset vendor-revision %REVISION% .
svn merge vendorurl@%VENDOR_REVISION% vendorurl@%REVISION% .
This procedure seems simple enough I was thinking perhaps it could
even be exposed through the UI with a create vendor branch enter url
and optional revision the url would be imported and info saved into a
couple of properties. Another UI command update vendor branch could
ask you which revision to update to and then perform the merge into
working copy, therefore making vendor branches easy to create and
update and without creating unnecessary copies of the vendor source
code (assuming it exists in another svn repository anyway).
Thanks,
- Kurt Harriger
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1211215
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-02-23 07:02:49 CET