You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm trying to migrate a SVN repsitory which has some tags with following names: ${version.technical}, ${BUILD_NUMBER}. (These tag names have bveen created when tagging from jenkins)
svn2git runs fine when adding --notags flag, but I want to include all tags but these 2 in the git repo.
Tested lots of combinations of --exclude flag, but i'm no sure which syntax should I use ...
Now, i'm getting this: creating empty directory: repo-name/src/main/resources/js/test sh: svn/tags/${version.technical}: bad substitution command failed: git log -1 --pretty=format:'%s' "svn/tags/${version.technical}" command failed: git config --local --unset user.name
BTW, --exclude './tags/.' should be equivalent to --notags flag, right?
Removing these 2 tags in the current SVN does not help us because these tags still exist in the repo's history. How can we scape the ${} chars?
The text was updated successfully, but these errors were encountered:
Hi,
I'm trying to migrate a SVN repsitory which has some tags with following names: ${version.technical}, ${BUILD_NUMBER}. (These tag names have bveen created when tagging from jenkins)
svn2git runs fine when adding --notags flag, but I want to include all tags but these 2 in the git repo.
Tested lots of combinations of --exclude flag, but i'm no sure which syntax should I use ...
Now, i'm getting this:
creating empty directory: repo-name/src/main/resources/js/test sh: svn/tags/${version.technical}: bad substitution command failed: git log -1 --pretty=format:'%s' "svn/tags/${version.technical}" command failed: git config --local --unset user.name
BTW, --exclude './tags/.' should be equivalent to --notags flag, right?
Removing these 2 tags in the current SVN does not help us because these tags still exist in the repo's history. How can we scape the ${} chars?
The text was updated successfully, but these errors were encountered: