RE: Inter-Repository Communication

The best way to go about setting up a system like this would be a hook
based replication scenario that then invokes a merge on the appropriate
target tree. That little simple sentence involves a lot of concepts that
SVN really isn't set to handle atm. The biggest one is having SVN
support merging at all.

Bill

--
Bunnies aren't just cute like everybody supposes.
They got their hoppy legs and twitchy little noses.
And what's with all the carrots, 
What do they need such good eyesight for anyway?
-----Original Message-----
From: James Neal [mailto:neal@skylab.org] 
Sent: Friday, November 23, 2001 6:41 PM
To: dev@subversion.tigris.org
Subject: Inter-Repository Communication
Hi,
I'm just starting to play with svn, and just grabbed the source from
the svn repo for the first time a few days ago.  
One piece I'm _really_ interested in the idea of Inter-Repository
Communication, presented in the "Blue Sky Ideas" section of the Design
document.  I realize this section is for lower-priority tasks, but
before
I start working on it, I was wonder if anyone else was.
-James
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org