> Thanks for all the replies! Let me attempt to clarify:
> The master repository is owned and operated by group 1 and group 2 is only allowed to checkout the code. Group 2 wants to be able to check their changes in somewhere and share those changes amongst themselves.
> I guess I'm just asking if it's possible to set up this 2nd repository and checkin the original code plus some modifications, and if it would work to do and svn switch to go back to the original repository to take any new changes (and then switch back to the 2nd repository).
No, there is no handy way to maintain history in separate repositories.
The best scenario would be if group 1 would create a branch copy and
give group 2 write access. This would permit changes in the branch copy
that did not affect the group 1 copy, yet changes/updates could be
Otherwise you have to follow the 'vendor drop' scenario to put snapshots
of code from group 1 into the group 2 repository and prepare diffs that
someone in group 1 could apply if you ever want to send changes back.
There are several tools to tie subversion to a remote-but-not-subversion
system, like svk, or git-svn. I'm not sure if the git tools are
sufficiently usable now to make the latter a good choice or not.
Conceptually, it pulls a copy from a subversion target which you branch
for your changes and you can subsequently pull updates from the
subversion side or push your changes back (if you had write access) but
locally you'd be using git with your branch copy.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-06 00:56:33 CEST