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

Re: Subversion vendor branch revisited...

From: Ph. Marek <philipp.marek_at_bmlv.gv.at>
Date: 2006-02-02 15:24:13 CET

On Thursday 02 February 2006 15:21, Doyle, Patrick wrote:
> I had a bizarre thought yesterday and thought I would pass it on to the
> list for comments...
> Suppose I modified Subversion such that the name of the ".svn" directory
> was specified by an environment variable (such as SVN_META_DIR) instead of
> being hard coded in the client code. Then I could do things like:

As I don't really know the implications of these changes, eg. importing
the .svn in one repository, the .svn.vendor in the other, with corresponding
problems when updating one to an older version (trashing the information of
the other repository), etc....

I'd suggest using svk - it should do what you need, ie. mirror a remote
repository, ease working on local branches, and supports generating patches.

That seems *much* better than having one working copy disturbing another,
laying beneath/over the other ...



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 2 15:26:29 2006

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