Matt Good wrote: > The easiest way I've found to do distributed version control with > Subversion is via SVK. It lets you mirror a Subversion repository, > record your local changes, and continue to merge in upstream changes. > > See http://svk.bestpractical.com/view/HomePage
If I understand right, this tools is for local branches which are _not_ published on a remote server. - I've currently this setup: my decentral branch repository: http://dev.lazaridis.com/base/browser/infra/trac-dev I've a standard local working copy of this. I've a standard local working copy of the original trac-dev-repo, too. - I do my custom changes within the local trac-dev-repo copy. I checkout new versions of trac, detecting conflicts and doing the merges manually. then I simply export the working-copy files to my decentral-branch-working-copy, overwriting the existen files with the new changes. [1] then I commit those to the decentral-branch-repo (making them available to other developers) everything fine so far. - Problem: files removed from the trac-dev-repo are automaticly removed in the trac-dev-working-copy. [1[ but they remain within the decentral-branch-working-copy, Any standard solution to this? - http://dev.lazaridis.com/base/wiki/PlanDecentralBranching --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
