git-svn: multiple fetch/branches/tags keys are supported
"git svn" can be configured to use multiple fetch, branches, and tags refspecs by passing multiple --branches or --tags options at init time or editing the configuration file later, which can be handy when working with messy Subversion repositories. Add a note to the configuration section documenting how this works. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Eric Wong <normalperson@yhbt.net>
Nathan Gray committed
Dec 19, 2011 at 19:23 UTC
eff714bddafd3d49cde0eac6ae670970da024fb4
1 file changed
+12
Documentation/git-svn.txt
+12
@@ -1032,6 +1032,18 @@ comma-separated list of names within braces. For example:
1032
tags = tags/{1.0,2.0}/src:refs/remotes/tags/*
1033
------------------------------------------------------------------------
1034
1035
+Multiple fetch, branches, and tags keys are supported:
1036
+
1037
+------------------------------------------------------------------------
1038
+[svn-remote "messy-repo"]
1039
+ url = http://server.org/svn
1040
+ fetch = trunk/project-a:refs/remotes/project-a/trunk
1041
+ fetch = branches/demos/june-project-a-demo:refs/remotes/project-a/demos/june-demo
1042
+ branches = branches/server/*:refs/remotes/project-a/branches/*
1043
+ branches = branches/demos/2011/*:refs/remotes/project-a/2011-demos/*
1044
+ tags = tags/server/*:refs/remotes/project-a/tags/*
1045
+------------------------------------------------------------------------
1046
+
1047
Note that git-svn keeps track of the highest revision in which a branch
1048
or tag has appeared. If the subset of branches or tags is changed after
1049
fetching, then .git/svn/.metadata must be manually edited to remove (or