On 10/9/07, BUNBURY Myles <Myles.Bunbury@alcatel-lucent.com> wrote:
> Periodically I run into the following scenario. What is the best (ie.
> quickest/simplest/least error prone) way to accomplish this?
>
>
> I am connected to two separate, independent SVN repositories, A & B.
>
> I only have read access to repository A. I have read & write access to
> Repository B.
>
> Repository A has periodic commits as others make changes to the source.
> I also make some changes to the code in repository A; however, these are
> not committed to repository A since I don't have write access.
>
> To backup & keep track of the changes I make to repository A, I
> periodically commit my working copy of repository A to repository B.
> Repository B therefore becomes a snapshot of repository A, reflecting
> all the 'official' changes made to repository A plus my own custom
> changes. I'm looking for a quick, simple, and human error resistant way
> to accomplish this. Effectively, I want to tell SVN to make repository B
> look like my working copy of repository A, and therefore have SVN
> automatically do whatever adds/deletes/modifies are necessary to achieve
> this.
>
>
> Thoughts?
You need a distributed revision control tool: svk if you need to
exchange with Subversion repositories. (See svk.elixus.org)
HTH,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 9 14:59:32 2007