svn-externals

SVN externals repo “is already locked” on update

我怕爱的太早我们不能终老 提交于 2019-12-06 17:11:28
问题 Basically I have to repo on the same server: svn://repo/foo -> checked out to d:\foo svn://repo/bar -> d:\foo has an svn:external property set to check this out into d:\foo\bar When an "svn:update" or a new "svn:checkout" this is gist of the error: Command - Update Updated - D:\foo External - D:\foo\bar External failed - D:\foo\bar Error - d:\foo\bar is already locked via d:\foo After I "clean" or manually release the lock, the problem still persists. Any insights would be greatly appreciated

Migrate from svn to git keeping svn-externals

…衆ロ難τιáo~ 提交于 2019-12-06 07:47:43
I am migrating from an svn repository to git. This svn repository has svn-externals, to be kept on svn repositories. These external are versioned and tagged in the history, and are read only. How I can properly migrate and have the svn-externals in the new git repository properly set? I am looking in "git svn propset", git submodules, subtree merges. But How I can set up such a repository? Alternatively, I propose: Use a modified version of this simple old python script, that works: https://github.com/eneroth/git-externals This script would check out all svn:externals previously defined in

REGEX for svndumptool

拟墨画扇 提交于 2019-12-06 04:17:36
问题 I have a large (30+GB) legacy SVN repo with a lot of externals defined that needs to be cloned to a new server. As the repo was originally created in the pre SVN v1.5 days it has a lot of externals defined with absolute paths that refer back to the old server name. I want to remove all the absolute paths and make them relative so that the migration will work. I found svndumptool via this question, it works great on some of the externals but I haven't been able to figure out a REGEX that will

How to deal with partial svn:externals when migrating to Git?

跟風遠走 提交于 2019-12-05 11:58:24
I would like to import a SVN repository into a GitHub Enterprise repository There are many questions related to this matter and most of them can be addressed either with Git submodules or Git subtree. In my case I have two repositories: The main project repository The modules repository (a big SVN repository over 2 GB) This module repository has the following architecture: foolib/ moduleA/ ... moduleB/ ... ... For the project, only few modules from foolib are used as svn:externals . For example this main project only uses moduleA from foolib . As mentioned in this question one possible

How to set a revision number for svn external?

喜夏-厌秋 提交于 2019-12-05 07:15:45
So I have this file Mobile.framework and if I do a svn propedit i get svn propedit svn:externals It brings up Mobile.embeddedframework svn+ssh://../Mobile.embeddedframework This is pointed to the head. I want to edit this and set it to -r1209. Whats the correct way to set it to a revision? Have a look at the SVN manual : Mobile.framework svn+ssh://../Mobile.embeddedframework@100 - note the @100 . (or) svn propedit svn:externals . can help you edit it. svn propset svn:externals \ Mobile.framework svn+ssh://../Mobile.embeddedframework@1024 1024 is arbitrary :) replace it with the revision number

when updating a whole project's root, how to exclude svn externals from being updated?

霸气de小男生 提交于 2019-12-05 03:47:16
Is there a way to exclude all svn externals when doing a recursive update? Is there a way to exclude only 1 of all of the svn externals when doing a recursive update? Basically I'd like to cut down the svn update time, and a couple of the SVN externals that I have will just about never get updated. Yes, there is an option for this (to ignore all): > svn update --ignore-externals I don't know of any option to specifically ignore one or some externals while updating the rest. If you are using TortoiseSVN, you can do the same thing as "svn update --ignore-externals". Use the " Update to revision.

SVN externals repo “is already locked” on update

扶醉桌前 提交于 2019-12-04 22:46:58
Basically I have to repo on the same server: svn://repo/foo -> checked out to d:\foo svn://repo/bar -> d:\foo has an svn:external property set to check this out into d:\foo\bar When an "svn:update" or a new "svn:checkout" this is gist of the error: Command - Update Updated - D:\foo External - D:\foo\bar External failed - D:\foo\bar Error - d:\foo\bar is already locked via d:\foo After I "clean" or manually release the lock, the problem still persists. Any insights would be greatly appreciated. Thanks! Update: Attila nailed it in the comment. I had "foo/bar" existing in the repository. For

git svn - clone repo with all externals

我是研究僧i 提交于 2019-12-04 11:13:23
问题 I want to use git to clone a svn repository, but unfortunately, where svn checkout gets the repo with all externals, git svn clone only gets the repository without externals. How can I get the externals from the svn repository via git svn ? I don't want to do any fancy stuff, just get the the complet repo with externals. 回答1: git-svn doesn't support externals, but you may try SmartGit instead of git-svn. It supports svn:externals, converting them into .gitsvnextmodules file and displaying as

How to have TortoiseSVN always freeze svn:externals for tags

扶醉桌前 提交于 2019-12-03 08:43:57
问题 Is this possible with tortoiseSVN?: Always freeze svn:externals for tags the scenario is our trunk will always use the 'HEAD' revision for externals, however when we create 'tags' we would like for them to have a revision set for externals to properly 'freeze' them at a specific point in time. Update Thanks to everyone for your feedback/info. Since I could not find anything that would completely meet our needs (tried smartsvn and svncopy.pl ) I made a console app that so far has passed all

git svn - clone repo with all externals

回眸只為那壹抹淺笑 提交于 2019-12-03 07:12:15
I want to use git to clone a svn repository, but unfortunately, where svn checkout gets the repo with all externals, git svn clone only gets the repository without externals. How can I get the externals from the svn repository via git svn ? I don't want to do any fancy stuff, just get the the complet repo with externals. git-svn doesn't support externals, but you may try SmartGit instead of git-svn. It supports svn:externals, converting them into .gitsvnextmodules file and displaying as modules. The only restriction: you should clone the repository with SmartGit instead of opening already