Add branches to docs, be a bit more specific

diff --git a/docs/fdroid.texi b/docs/fdroid.texi
index ab361b745e3dead8655dd5c83103159a43dd62e8..d898a2f48caf10f3427b8d0fe14fc326563ff224 100644 (file)
--- a/docs/fdroid.texi
+++ b/docs/fdroid.texi
@@ -638,9 +638,14 @@ The git-svn option connects to an SVN repository, and you specify the URL in
 exactly the same way, but git is used as a back-end. This is preferable for
 performance reasons, and also because a local copy of the entire history is
 available in case the upstream repository disappears. (It happens!). In
-order to use Tags as update check mode for this VCS type
-the URL must encode the path to the trunk and tags, like so: 
-http://svn.code.sf.net/p/project/code;trunk=trunk;tags=tags.
+order to use Tags as update check mode for this VCS type, the URL must have
+the tags= special argument set. Likewise, if you intend to use the
+RepoManifest/branch scheme, you would want to specify branches= as well.
+Finally, trunk= can also be added. All these special arguments will be passed
+to "git svn" in order, and their values must be relative paths to the svn repo
+root dir.
+Here's an example of a complex git-svn Repo URL:
+http://svn.code.sf.net/p/project/code/svn;trunk=trunk;tags=tags;branches=branches
 
 For a Subversion repo that requires authentication, you can precede the repo
 URL with username:password@ and those parameters will be passed as @option{--username}