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

Mixing two repositories

From: Alan Chandler <alan_at_chandlerfamily.org.uk>
Date: 2005-01-03 00:33:57 CET

A number of open source projects provide access to their source code
repositories via (currently) cvs. Normally I will not have anything other
that anonymous access to them, but I want to work on my own modifications
(maybe just debugging statements looking for bugs - but sometimes a personal
enhancement), and if eventually there is a change worthy of submission back
to the main project, I can do this as a patch against the their HEAD version.

It is possible to checkout this code, and then import it as a "vendor" branch
in a local svn repository. I can then take "copies" from this branch and
then make my own modifications (often exploring different directions with
different branches). Every so often I will get an update from the main
repository, following the procedure in the book using svn merge to keep my
own branch up to date with the main project.

The question I have is - will this still work if any of them switch from cvs
to svn as their repositories?

The problem I forsee is the double role that the .svn directories are supposed
to play in this scenario (holding meta information for the remote repository
as well as my local one). Is there a modus operandi that I can use in these
circumstances to avoid the problem?

Alan Chandler
First they ignore you, then they laugh at you,
 then they fight you, then you win. --Gandhi
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 3 00:36:04 2005

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.