On Oct 11, 2006, at 09:41, Carroll, Andrew wrote:
> At our work we currently use SVN to manage our projects and files.
> We do this by the checkout, modify and commit cycle or whatever you
> want to call it. Problem is, once I check it out, I have no way
> (other than making folders) to track my changes to the working
> copy. I want to track my local changes using SVN and then somehow
> get them from a local SVN to the work SVN. I normally start out by
> checking out a working copy to my local area. I want that checkout
> to go into my local SVN and then check out from my local SVN so I
> can track my own changes.
>
>
>
> I don’t however know what process is involved in getting the local
> SVN up to the work SVN. What is that process called?
>
>
>
> If this question has been posted before then just tell me to go
> read the history of this list (maybe you could give me some search
> terms though). Thanks.
Subversion doesn't really work that way; it requires a single write-
enabled central repository. But you want there to be multiple
writeable repositories that can send their changes back and forth, so
you may want to look into SVK, which is built on the Subversion
libraries and does work that way, from what I understand. Their web
page:
http://svk.bestpractical.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 11 19:01:17 2006