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

Re: CVS / Subversion interoperability

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: 2006-12-22 20:11:51 CET

On Fri, 2006-12-22 at 15:29 +0000, Robert Swarbrick wrote:
> I have this working as an initial experiment on my system. Which is fine
> for my personal use, but persuading a team to remember to commit to both
> repositories at the same time will be awkward.
> Getting the initial directory involved having both checked out into two
> separate directories, then physically copying one directory tree on top
> of the other - I couldn't find any other way of persuading either
> Subversion or CVS to do a checkout (to create the CVS / .svn
> directories) when there was already a bunch of files and directories
> existing - "in the way".

What happens if someone else commits a change in both repostories, then
you do an update? One or the other of the systems is going to think
you need patches based on your current revision that the other system
has already made to your working copy.

  Les Mikesell
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 22 20:12:35 2006

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.