summaryrefslogtreecommitdiff
path: root/t/t9154-git-svn-fancy-glob.sh
diff options
context:
space:
mode:
authorJay Soffian <jaysoffian@gmail.com>2010-01-23 03:30:00 -0500
committerEric Wong <normalperson@yhbt.net>2010-01-23 03:23:04 -0800
commit3e18ce1ac3034b1562ec748523aa7636e1b58b52 (patch)
treed4876c45fb29fbbb42e2a27f8be310c321520edd /t/t9154-git-svn-fancy-glob.sh
parentc79f1189bc4e7d9bb9cb673c043ce8f587a9a92d (diff)
downloadgit-3e18ce1ac3034b1562ec748523aa7636e1b58b52.tar.gz
git-svn: allow UUID to be manually remapped via rewriteUUID
In certain situations it may be necessary to manually remap an svn repostitory UUID. For example: o--- [git-svn clone] / [origin svn repo] \ o--- [svnsync clone] Imagine that only "git-svn clone" and "svnsync clone" are made available to external users. Furthur, "git-svn clone" contains only trunk, and for reasons unknown, "svnsync clone" is missing the revision properties that normally provide the origin svn repo's UUID. A git user who has cloned the "git-svn clone" repo now wishes to use git-svn to pull in the missing branches from the "synsync clone" repo. In order for git-svn to get the history correct for those branches, it needs to know the origin svn repo's UUID. Hence rewriteUUID. Signed-off-by: Jay Soffian <jaysoffian@gmail.com> Acked-by: Eric Wong <normalperson@yhbt.net>
Diffstat (limited to 't/t9154-git-svn-fancy-glob.sh')
0 files changed, 0 insertions, 0 deletions