Subversion vendor branch revisited...
From: Doyle, Patrick <WPD_at_dtccom.com>
Date: 2006-02-02 15:21:18 CET
I had a bizarre thought yesterday and thought I would pass it on to the list
I have a situation where I am integrating 3rd party code, which is supplied
Sometimes, I would like to feed patches back to the developer for the 3rd
I definitely want a copy of the vendor's code on my server so that I can
On the one hand, this sounds like a classic "vendor branch" scenario where I
Then I started thinking (now, you all _know_ I'm in trouble). Since the
Then I started thinking, "Gee that would take me a while to get right,
Here's where it starts to get bizarre...
Suppose I modified Subversion such that the name of the ".svn" directory was
$ SVN_META_DIR=.svn.vendor svn co svn://vendor/path/to/repos
to check out the vendor tree, and
$ svn import ...
to check it into my subversion server.
Later, to find out what I've modified locally I could do:
$ svn status
To find out what I've changed relative to the vendor's code, I could do:
$ SVN_META_DIR=.svn.vendor svn status
What do folks think of this?
--wpd
---------------------------------------------------------------------
|
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.