Hi Sam, On 5/24/07, Sam Vilain <sam@xxxxxxxxxx> wrote:
However, you are in a relatively obscure use case, most projects wouldn't do this. Note also that the merge tickets SVK would use are
hm I am not looking for a complete bidirectional flow. I have a project (say my great open source project) in svn for which I have only read access. Since I don't have a write access, I have a personal svn sandbox for which I have complete read-write access and I branch the trunk into this svn sandbox. I commit all my changes to my sandbox so that I don't loose all my data in case my system fails! I also setup a local branch to which I can commit when I don't have a network access. With Svk it has been (skipping the local branch step for now) svk mirror <myproject_svn_url>/trunk //trunk svk mirror <myproject_svn_sandbox_url>/mybranch //mybranch svk smerge --baseless //trunk //mybranch -m 'first merge' I also have a local branch in svk: (local branch setup) svk copy //mybranch //localbranch -m 'local svk branch' and occasionally enter the following commands to get the latest in trunk: svk smerge //trunk //mybranch or svk smerge //mybranch //localbranch
the UUID and revision numbers in the property will not refer to revisions in svn://svn.paris.fr/ but to the (private) SVN repository in the SVK depot.
that is scary since I am not sure if I still have that local repository now. I would look into your patch suggestion for sure, but also open for other suggestions . I am thinking if I should host the project in a different public git server (for now) instead of my svn sandbox and it will be easier :). -- Vinu In a world without fences who needs Gates? - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
