You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by James Neal <ne...@skylab.org> on 2001/11/24 02:40:46 UTC

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

Re: Inter-Repository Communication

Posted by Yoshiki Hayashi <yo...@xemacs.org>.
Greg Stein <gs...@lyra.org> writes:

> > If you are subscribed to svn@subversion.tigris.org, I think
> > you saw my series of commit in short time period.  Those
> > changes are copied from my local repository of ruby binding.
> > It works for me because I'm the only one who changes
> > bindings/ruby area right now.
> 
> Not quite true. Karl modified delta_editor.c to deal with the renaming of
> "replace_*" to "open_*".

Oops.  I didn't notice that.  That was on second line of the
changed section in commit mail.  I don't know why I missed
that.

> Other people may be be updating the Ruby area when changes are made to APIs,
> to keep the stuff in sync. They won't be able to make certain changes, of
> course. But since people can/will make those changes, you're going to need
> to update your scripts to deal with that.

My script is supposed to deal with that by bombing out with
conflict error as usual.  But I modified local ra_dav to get
DAV:checked-in property from server instead of local working
copy and probably that's the cause of the bug.  My first
intention was to post that patch to see the change is
correct and then use my script to upload ruby binding
changes but I upload my changes first thinking 'OK, this
works in local tests.  Let's just commit them first'.
Sorry, I'll be more careful in the future.

How many times did I say this sentence?  I should leran more
quickly. :-(

> And you probably ought to re-apply Karl's changes.

Done.

-- 
Yoshiki Hayashi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Inter-Repository Communication

Posted by Greg Stein <gs...@lyra.org>.
On Mon, Nov 26, 2001 at 09:49:23PM +0900, Yoshiki Hayashi wrote:
>...
> If you are subscribed to svn@subversion.tigris.org, I think
> you saw my series of commit in short time period.  Those
> changes are copied from my local repository of ruby binding.
> It works for me because I'm the only one who changes
> bindings/ruby area right now.

Not quite true. Karl modified delta_editor.c to deal with the renaming of
"replace_*" to "open_*".

> Oh, I found that my script messed up
> bindings/ruby/delta_editor.c.  It worked fine on my local
> system but I need to find out what went wrong.

Probably the fact that Karl updated the files.

It is also important to note that you blew away Karl's changes.

Other people may be be updating the Ruby area when changes are made to APIs,
to keep the stuff in sync. They won't be able to make certain changes, of
course. But since people can/will make those changes, you're going to need
to update your scripts to deal with that. And you probably ought to re-apply
Karl's changes.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Inter-Repository Communication

Posted by Yoshiki Hayashi <yo...@xemacs.org>.
James Neal <ne...@skylab.org> writes:

> 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.

I have written very primitive support for it in Ruby.  It's
called svndist.rb in my workspace.  It's not ready for
general public until Subversion supports merging but the
basic concept works.

If you are subscribed to svn@subversion.tigris.org, I think
you saw my series of commit in short time period.  Those
changes are copied from my local repository of ruby binding.
It works for me because I'm the only one who changes
bindings/ruby area right now.

Oh, I found that my script messed up
bindings/ruby/delta_editor.c.  It worked fine on my local
system but I need to find out what went wrong.

I need to go home now but I can elaborate if you are
interested.

-- 
Yoshiki Hayashi

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Inter-Repository Communication

Posted by Ben Collins-Sussman <su...@collab.net>.
James Neal <ne...@skylab.org> writes:

> 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.

Sorry, hasn't been discussed, and probably won't be until we hit 1.0.
:-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

RE: Inter-Repository Communication

Posted by Bill Tutt <ra...@lyra.org>.
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