lorry: bundle support

A bundle policy and destination can be specified in settings
It will bundle up tags and branches

Some changes to fetching were required, now it only fetches origin and expects that
the refspec fetches into local refs. svn support has been altered to support this

1 files changed, 15 insertions, 7 deletions

diff --git a/README b/README
index 10d5d2b..ce43ea7 100644
--- a/README
+++ b/README
@@ -86,13 +86,6 @@ is assumed to be the master branch.
 	}
 
 ### Subversion
-Subversion can be used similarly to git if only one branch is needed
-	{
-	    "mpc": {
-	        "type": "svn",
-	        "url": "svn://scm.gforge.inria.fr/svn/mpc/trunk",
-	    }
-	}
 To support all the branches and tags a layout needs to be specified as svn is
 very flexible with the possible layouts, however the most common is to have the
 working branch in a directory called trunk, and the branches and tags in 
@@ -148,6 +141,21 @@ Netpbm for example, keeps all its branches in the root directory
 	    }
 	}
 
+Note that git-svn can provide better history tracking if the url is as close to
+the root of the repository as possible, so it may be more effective if the lorry
+was specified similar to this, assuming svnroot is the real root of the repo
+	{
+	    "netpbm": {
+		"type": "svn",
+		"url": "https://netpbm.svn.sourceforge.net/svnroot/",
+		"layout": {
+		    "trunk": "netpbm/trunk",
+		    "branches": "netpbm/{advanced,stable,super_stable}",
+		    "tags": "netpbm/release_number/*"
+		}
+	    }
+	}
+
 ### CVS
 The url for CVS repositories is the CVSROOT string. The module is required as
 cvs repositories usually have multiple modules, the module is usually the same