From b781147b4d8e107a249470d53fef07ee19e421d2 Mon Sep 17 00:00:00 2001 From: Tony Duckles Date: Sat, 7 Apr 2012 20:24:23 -0500 Subject: [PATCH] README updates --- README.mkd | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-) diff --git a/README.mkd b/README.mkd index e385492..fd0a0b1 100644 --- a/README.mkd +++ b/README.mkd @@ -6,7 +6,8 @@ Features -------- - **Meant for replaying history into an "empty target location**. This could be an empty target repo or simply an empty folder/branch in the target repo. -- **Maintains logical history (when possible)**, e.g. uses "svn copy" for renames. +- **Maintains logical history (ancestry) when possible**, e.g. uses "svn copy" + for renames. - **Maintains original commit messages**. - **Optionally maintain source commit authors (`svn:author`) and commit timestamps (`svn:date`)**. Requires a "pre-revprop-change" hook script in the target @@ -21,6 +22,14 @@ Features to give the ability to dynamically exclude or modify files as part of the replay. +Requirements +------------ +- **Python 2.6** or higher. +- **Subversion 1.6** or higher. +- Written for a UNIX-type environment, e.g. Linux, Mac OSX, etc. For + Windows-based usage, recommend using [Cygwin](http://www.cygwin.com/) for + best compatibility. + Overview -------- This is a utility for replicating the revision history from a source path in @@ -34,19 +43,21 @@ history which is taking up a lot of disk-space and not serving a lot of purpose going forward. You can this utility to replay/filter just the "/trunk" SVN history into a new repository, so that things like "svn log" and "svn blame" will still show the correct (logical) history/ancestry, even though we end-up -generating new commits which will have newer commit-dates and revision #'s. +generating new commits which will have newer commit-dates and revision #'s +(_though this script can optionally maintain the original commit-dates and +revision #'s if desired_). -While this replay will obviously run faster if you're running between both -a local source and target repositories, none of this *requires* direct +While this replay process will obviously run faster if you're running between +both a local source and target repositories, none of this *requires* direct access to the repo server. You could access both the source and target repo's -over standard `http://`, `ssh://`, etc. methods. +over standard `http://`, `svn://`, `svn+ssh://`, etc. methods. Usage ----- See `svn2svn.py --help`: $ ./svn2svn.py --help - svn2svn, version 1.4.0 + svn2svn, version 1.5.0 Usage: svn2svn.py [OPTIONS] source_url target_url -- 2.43.0