view tests/fixtures/empty_dir_in_trunk_not_repo_root.svndump @ 787:4bbc6bf947f5 1.2.1

replay: fetch full revision at most once per run (issue252) Before this change, hgsubversion was fetching full revisions from the first revision the project was created to the first revision containing converted data. Unfortunately, some projects exhibits such spans longer than 500 revisions, during which hgsubversion was uselessly scanning the whole tree. The fix is not technically perfect, we could record somewhere that while no data was converted we scanned the project already, instead of scanning once at every hgsubversion run until a revision is converted. But it should be good enough unless someone runs hgsubversion once for every target revision. One repository exhibiting this behaviour: svn://svn.zankasoftware.com/zanka
author Patrick Mezard <pmezard@gmail.com>
date Sun, 13 Feb 2011 20:10:52 +0100
parents 6ec5b5fc5b4d
children
line wrap: on
line source

SVN-fs-dump-format-version: 2

UUID: c866b883-4c03-404b-8609-dade481701a6

Revision-number: 0
Prop-content-length: 56
Content-length: 56

K 8
svn:date
V 27
2009-04-15T03:39:30.544797Z
PROPS-END

Revision-number: 1
Prop-content-length: 104
Content-length: 104

K 7
svn:log
V 5
trunk
K 10
svn:author
V 5
durin
K 8
svn:date
V 27
2009-04-15T03:39:31.069518Z
PROPS-END

Node-path: project
Node-kind: dir
Node-action: add
Prop-content-length: 10
Content-length: 10

PROPS-END


Node-path: project/trunk
Node-kind: dir
Node-action: add
Prop-content-length: 10
Content-length: 10

PROPS-END


Revision-number: 2
Prop-content-length: 118
Content-length: 118

K 7
svn:log
V 18
file and empty dir
K 10
svn:author
V 5
durin
K 8
svn:date
V 27
2009-04-15T03:39:32.069497Z
PROPS-END

Node-path: project/trunk/a
Node-kind: file
Node-action: add
Prop-content-length: 10
Text-content-length: 2
Text-content-md5: 60b725f10c9c85c70d97880dfe8191b3
Content-length: 12

PROPS-END
a


Node-path: project/trunk/narf
Node-kind: dir
Node-action: add
Prop-content-length: 10
Content-length: 10

PROPS-END