view tests/fixtures/truncatedhistory.sh @ 225:2117cb0118fe

Get rid of .hg/svn/last_rev: We now calculate the last known revision by iterating over all known revisions and finding the highest number. Theoretically, we might be able to simply read the latest entry, but in practice, that's a bug waiting to happen. For instance, we might want to achieve compatibility with '.hg/shamap' as generated by the ConvertExtension, and it not only cannot offer a guarantee of linearity, but it also allows more than one conversion to source exists. I'd say we have other problems to care about until this turns up as a hotspot in profiling. Such as why we leak circa 100MB of memory per 1000 revisions converted ;)
author Dan Villiom Podlaski Christiansen <danchr@gmail.com>
date Fri, 27 Mar 2009 01:09:36 +0100
parents 3b60f223893a
children
line wrap: on
line source

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

mkdir temp
cd temp

mkdir project-orig
cd project-orig
mkdir project1
mkdir project2
cd ..

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

svn co $svnurl project
# Make a single revision in trunk
cd project/project1
echo a > a
svn add a
svn ci -m "add a"
cd ..
svn up
# Rename the project
svn mv project1 project2/trunk
svn ci -m "rename project1"
cd project2/trunk
echo b > b
svn add b
svn ci -m "add b"
cd ../../..

svnadmin dump testrepo > ../truncatedhistory.svndump