sapling/tests/fixtures/revert.sh

#!/bin/sh
#
# Generate revert.svndump
#

rm -rf temp
mkdir temp
cd temp
mkdir -p import/trunk/dir
cd import/trunk
echo a > a
echo b > dir/b
cd ../..

svnadmin create testrepo
svnurl=file://`pwd`/testrepo
svn import import $svnurl -m init

svn co $svnurl project
cd project
echo a >> trunk/a
echo b >> trunk/dir/b
svn ci -m changefiles
svn up
# Test directory revert
svn rm trunk
svn cp $svnurl/trunk@1 trunk
svn st
svn ci -m revert
svn up
# Test file revert
svn rm trunk/a
svn rm trunk/dir/b
svn cp $svnurl/trunk/a@2 trunk/a
svn cp $svnurl/trunk/dir/b@2 trunk/dir/b
svn ci -m revert2
cd ..

svnadmin dump testrepo > ../revert.svndump
stupid: do not close branch upon branch-wide revert Reverting a branch with a remove followed by a copy results in a branch replacement. By default, branch replacements are handled by closing the replaced branch and committing the new branch on top of it. But we do not really want that when reverting a branch, we only want a linear history with a changeset capturing the revert. 2012-10-16 23:17:55 +04:00			`#!/bin/sh`
			`#`
			`# Generate revert.svndump`
			`#`

			`rm -rf temp`
			`mkdir temp`
			`cd temp`
			`mkdir -p import/trunk/dir`
			`cd import/trunk`
			`echo a > a`
			`echo b > dir/b`
			`cd ../..`

			`svnadmin create testrepo`
			svnurl=file://`pwd`/testrepo
			`svn import import $svnurl -m init`

			`svn co $svnurl project`
			`cd project`
			`echo a >> trunk/a`
			`echo b >> trunk/dir/b`
			`svn ci -m changefiles`
			`svn up`
			`# Test directory revert`
			`svn rm trunk`
			`svn cp $svnurl/trunk@1 trunk`
			`svn st`
			`svn ci -m revert`
			`svn up`
			`# Test file revert`
			`svn rm trunk/a`
			`svn rm trunk/dir/b`
			`svn cp $svnurl/trunk/a@2 trunk/a`
			`svn cp $svnurl/trunk/dir/b@2 trunk/dir/b`
			`svn ci -m revert2`
			`cd ..`

			`svnadmin dump testrepo > ../revert.svndump`